All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] skeleton: optionally wait for network interfaces to appear
Date: Wed, 28 Oct 2015 21:21:14 +0100	[thread overview]
Message-ID: <2419445.kGEUX5UIA3@sagittea> (raw)
In-Reply-To: <20151028174653.GA3650@free.fr>

Hello Yann,

On Wednesday 28 October 2015 18:46:53 Yann E. MORIN wrote:
> J?r?me, All,
> 
> 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 ;-).

> Also, I would have preferred patches 2 & 3 to be folded into a single
> patch. 
ok.

> I don't really understand how it all works:
> 
>   - does the busybox ifup-down and full-fledged ifup-down support
>     wait-delay?
Yes, both.

>   - 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."


>   - I guess 'wait-delay' is made an environment variable IF_WAIT_DELAY
> before the script is run, but I'd have preferred explanations rather
> than having to guess.
> 
> Care to shed some light, please?

Regards,

-- 
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr

  reply	other threads:[~2015-10-28 20:21 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 [this message]
2015-10-28 21:37       ` Yann E. MORIN
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=2419445.kGEUX5UIA3@sagittea \
    --to=jezz@sysmic.org \
    --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 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.