From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 28718@debbugs.gnu.org
Subject: [bug#28718] [PATCH] gnu: qemu: Add sysconfdir to configure-flags.
Date: Sun, 08 Oct 2017 17:22:44 +0200 [thread overview]
Message-ID: <87vajpekaj.fsf@gnu.org> (raw)
In-Reply-To: <87tvza3yaq.fsf@gmail.com> (Oleg Pykhalov's message of "Sun, 08 Oct 2017 10:15:41 +0300")
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> Hello Ludovic,
>
> ludo@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> I've used this patch to run a QEMU VM with bridge interface.
>>>
>>> $ mkdir -p /tmp/etc/qemu
>>> $ echo 'allow bridge0' | tee -a /tmp/etc/qemu/bridge.conf
>>> # ip link add bridge0 type bridge
>>> # ip link set dev enp6s0 master bridge0
>>> # ip link up bridge0
>>> # dhclient bridge0
>>> # qemu-system-x86_64 -net nic -net bridge,br=bridge0 # …
>>
>> It feels wrong to me to default to /tmp/etc instead of /etc.
>>
>> Setting up a bridge requires root privileges anyway, so why not stick to
>> /etc instead of /tmp/etc?
>
> It's inspired by libvirt package recipe :-)
Looking at commit a4b9392151 for libvirt, I think it’s a trick here: we
do pass --sysconfdir=/etc, and sysconfdir=/tmp/etc is passed only during
the install phase, which I think is a trick to avoid errors while
creating $(sysconfdir). But /etc is the actual sysconfdir AIUI.
So, WDYT? :-)
Ludo’.
next prev parent reply other threads:[~2017-10-08 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 3:30 [bug#28718] [PATCH] gnu: qemu: Add sysconfdir to configure-flags Oleg Pykhalov
2017-10-06 4:38 ` [bug#28718] Status: " Oleg Pykhalov
2017-10-07 17:58 ` [bug#28718] " Leo Famulari
2017-10-07 20:34 ` Ludovic Courtès
2017-10-08 7:15 ` Oleg Pykhalov
2017-10-08 15:22 ` Ludovic Courtès [this message]
2017-10-09 11:24 ` Oleg Pykhalov
2017-10-09 19:37 ` bug#28718: " Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vajpekaj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28718@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.