All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: RFC: auto eth0 and auto eth1 in netbase
Date: Mon, 10 Dec 2007 08:32:36 +0200	[thread overview]
Message-ID: <817303159.20071210083236@gmail.com> (raw)
In-Reply-To: <4759C1A2.3070308@student.utwente.nl>

Hello Koen,

Friday, December 7, 2007, 11:56:50 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> Khem Raj schreef:
>> On Nov 30, 2007 8:59 AM, Chris Larson <clarson@kergoth.com> wrote:
>>> On Nov 30, 2007 4:48 AM, Rod Whitby <rod@whitby.id.au> wrote:
>>>> Chris Larson wrote:
>>>>> Afaik, the execution of the hotplug/coldplug scripts on startup should
>>>>> generate the hotplug events for the ethernet interfaces and bring them
>>>>> up that way.  In debian, the hotplug scripts bring them up with ifup
>>>>> --allow=hotplug [iface], such that you need an 'allow-hotplug eth0' in
>>>>> interfaces to have them brought up that way.  I'm too rusty with OE to
>>>>> say how we do it today, but it's not likely that auto is needed.
>>>> Unfortunately, the busybox ifup applet does not support the
>>>> allow-hotplug keyword.
>>>>
>>>> Based on the feedback, I'll add 'auto eth0'.
>> 
>> fwiw with this change my nfsrooted rfs does not boot. I think its a
>> nice to have nfsroot option for dev work.

> doing any form of 'ifup' on the interface that connects to you nfsroot
> with shutdown the interface before trying to bring it up. I have the
> same problem on my PVR, and as a workaround I edited
> /path/to/nfs/etc/network/interface on the nfs server and removed the auto.
> Volunteers to teach ifup not to not close the link when using nfsroot?

  I've been having this issue in my queue. There're few problems with
current OE init scripts and nfsroot. I'm going to get to this one
sweet day, but if anyone gets to this earlier, even better ;-).

> regards,

> Koen




-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2007-12-10  6:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 11:53 RFC: auto eth0 and auto eth1 in netbase Rod Whitby
2007-11-29 12:58 ` Graeme Gregory
2007-11-29 14:16 ` mwester
2007-11-29 14:41 ` Koen Kooi
2007-11-29 17:02   ` Chris Larson
2007-11-30 11:48     ` Rod Whitby
2007-11-30 16:59       ` Chris Larson
2007-12-07 19:39         ` Khem Raj
2007-12-07 21:08           ` Rod Whitby
2007-12-07 21:56           ` Koen Kooi
2007-12-10  6:32             ` Paul Sokolovsky [this message]

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=817303159.20071210083236@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.