From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC][PATCH] netbase: don't start udhcpc if kernel assigned IP statically
Date: Tue, 22 Sep 2009 12:42:52 -0400 [thread overview]
Message-ID: <20090922164252.GA18271@denix.org> (raw)
In-Reply-To: <1253626112.16477.58.camel@lenovo.internal.reciva.com>
On Tue, Sep 22, 2009 at 02:28:32PM +0100, Phil Blundell wrote:
> On Mon, 2009-09-21 at 18:39 -0400, Denys Dmytriyenko wrote:
> > On Mon, Sep 21, 2009 at 08:45:06PM +0100, Phil Blundell wrote:
> > > It seems like there must be a better way of solving this problem. How
> > > about just teaching "ifup -a" to spot interfaces that are already up and
> > > leave them alone?
> >
> > Won't work for the case of kernel-acquired DHCP address, i.e. kernel level
> > autoconfig, aka IP_PNP, aka ip=dhcp command line.
>
> True, but your original patch won't help with this situation either
> (since "ip=dhcp" won't match the regex). I think this is a different
Not true. The default is to start udhcpc always. I just cover one case to
prevent it from starting when ip=x.x.x.x
> problem and probably requires a different solution: the ideal thing
> would be for the kernel to set a flag on the interface to say that it
> needs to be taken over by a DHCP client, or alternatively to invoke the
> DHCP client itself via the hotplug mechanism. Failing that you could
> arrange for the startup scripts to poke around at /proc/cmdline and try
> to second-guess what the kernel has done, although that would be rather
> less satisfactory.
next prev parent reply other threads:[~2009-09-22 16:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 16:07 [RFC][PATCH] netbase: don't start udhcpc if kernel assigned IP statically Denys Dmytriyenko
2009-09-21 19:45 ` Phil Blundell
2009-09-21 22:39 ` Denys Dmytriyenko
2009-09-22 8:54 ` Stanislav Brabec
2009-09-22 13:28 ` Phil Blundell
2009-09-22 16:42 ` Denys Dmytriyenko [this message]
2009-09-22 18:00 ` Phil Blundell
2009-09-22 18:32 ` Denys Dmytriyenko
2009-09-21 20:46 ` Koen Kooi
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=20090922164252.GA18271@denix.org \
--to=denis@denix.org \
--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.