From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] skeleton: optionally wait for network interfaces to appear
Date: Wed, 28 Oct 2015 22:37:02 +0100 [thread overview]
Message-ID: <20151028213702.GB3650@free.fr> (raw)
In-Reply-To: <2419445.kGEUX5UIA3@sagittea>
J?r?me, All,
On 2015-10-28 21:21 +0100, J?r?me Pouiller spake thusly:
> On Wednesday 28 October 2015 18:46:53 Yann E. MORIN wrote:
> > On 2015-10-28 16:59 +0100, J?r?me Pouiller spake thusly:
> [...]
> > Please drop the empty lines.
> There were empty lines in original patch ;-).
OK, I see. ;-)
Still, please drop them next time, please.
[--SNIP--]
> > - I looked at man 5 interfaces, and there is no mention of
> > wait-delay,
>
> I have found documentation related to if-*.d scripts in section called
> "IFACE OPTIONS" of interfaces(5) of my debian.
>
> > - I don't see how 'wait-delay' translates to 'wait_iface'
>
> From interfaces(5):
>
> "Additionally, all options given in an interface definition stanza are
> exported to the environment in upper case with "IF_" prepended and
> with hyphens converted to underscores and non-alphanumeric characters
> discarded."
OK, thanks for the explanations. So there is no relation between the
'stanza' name and the script name, right?
Also, I read this in man 5 interfaces;
When ifupdown is being called with the --all option, before doing
anything to interfaces, if [sic] calls all the hook scripts (pre-up
or down) with IFACE set to "--all", LOGICAL set to the current value
of --allow parameter (or "auto" if it's not set), ADDRFAM="meta"
and METHOD="none". After all the interfaces have been brought up or
taken down, the appropriate scripts (up or post-down) are executed.
Since S40network calls 'ifup -a' and you added a pre-up script, I guess
it should filter out the '--all' interface and exit early in that case.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-10-28 21:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 15:59 [Buildroot] [PATCH 0/3] Alternative way to wait interfaces on bootup Jérôme Pouiller
2015-10-28 15:59 ` [Buildroot] [PATCH 1/3] Revert "package/initscripts: S40network: wait for network interfaces to appear" Jérôme Pouiller
2015-10-28 15:59 ` [Buildroot] [PATCH 2/3] skeleton: optionally wait for network interfaces to appear Jérôme Pouiller
2015-10-28 17:46 ` Yann E. MORIN
2015-10-28 20:21 ` Jérôme Pouiller
2015-10-28 21:37 ` Yann E. MORIN [this message]
2015-10-28 21:51 ` Peter Korsgaard
2015-10-28 21:57 ` Yann E. MORIN
2015-10-28 22:15 ` Peter Korsgaard
2015-10-29 7:53 ` Nicolas Cavallari
2015-10-29 8:08 ` Nicolas Cavallari
2015-10-28 15:59 ` [Buildroot] [PATCH 3/3] skeleton: wait interface to appear if dhcp is enabled Jérôme Pouiller
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=20151028213702.GB3650@free.fr \
--to=yann.morin.1998@free.fr \
--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