From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] package/initscripts: S40network: wait for network interfaces to appear
Date: Tue, 27 Oct 2015 23:39:21 +0100 [thread overview]
Message-ID: <562FFD19.8020204@mind.be> (raw)
In-Reply-To: <562F426C.4010500@green-communications.fr>
On 27-10-15 10:22, Nicolas Cavallari wrote:
> However, true virtual interfaces may also be defined in
> /etc/network/interfaces and created via a pre-up stanza:
>
> auto br0
> iface br0 inet static
> pre-up ip link add br0 type bridge
> post-down ip link del br0
> address 203.0.113.42
> netmask 255.255.255.0
>
> In this case, S40network will wait forever. However, if the feature
> was implemented via ifupdown pre-up hooks, then this use-case could
> actually work, since hooks are executed after pre-up stanzas. But that
> is maybe too complex for buildroot.
Actually, this sounds less complicated than the script we currently have.
At least, if both busybox and ifupdown behave the same way.
Does systemd use /etc/network/interfaces and/or the hooks?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-10-27 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 7:16 [Buildroot] [git commit] package/initscripts: S40network: wait for network interfaces to appear Peter Korsgaard
2015-10-26 20:07 ` Ryan Barnett
2015-10-26 20:23 ` Peter Korsgaard
[not found] ` <CADZ9A7pN8Tq8NzDbnNDjjSP0Y7Edvo7TbngcFNhttO+v+ybMXg@mail.gmail.com>
2015-10-26 20:56 ` Peter Korsgaard
2015-10-26 21:04 ` Yann E. MORIN
2015-10-26 21:24 ` Ryan Barnett
2015-10-27 9:22 ` Nicolas Cavallari
2015-10-27 22:39 ` Arnout Vandecappelle [this message]
2015-10-27 22:46 ` Peter Korsgaard
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=562FFD19.8020204@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox