All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Faith <jfaith@soundmetrics.com>
To: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH v2] busybox-1.11.3/busybox-1.13.2: enable backgrounding for udhcpc
Date: Tue, 15 Jun 2010 09:01:55 -0700	[thread overview]
Message-ID: <4C17A3F3.3000705@soundmetrics.com> (raw)
In-Reply-To: <4C172F19.30005@dcombus.com>

Henri Bragge wrote:
> Steffen Sledz wrote:
>   
>> * The former default behaviour was to exit with failure if lease is not
>>   immediately obtained. This results in permanent network disconnect if DHCP
>>   server is (accidentally) not available at boot time. :(
>>
>> * Since bb 1.14 this is no longer hardcoded and can be configured.
>>     
>
> Works for me. I'm still not sure if -b should be hardcoded (it could be 
> passed through udhcpc_opts). On the other hand, if someone does not want 
> to leave udhcpc in the background they can just pass -n to it, which 
> seems to override -b. So this fix seems fine.
>
>   
I'd like to have 3 possible network modes: dhcp, zeroconf, or static IP 
and want to switch between them on-the-fly.  It looks like the non-dhcp 
modes can be done using a script or 2 in /etc/udhcpc.d, so it seems 
having udhcpcd running in the background would facilitate this.  Does 
that sound right?

,
John





  reply	other threads:[~2010-06-15 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  8:54 [PATCH] busybox-1.11.3/busybox-1.13.2: enable backgrounding for udhcpc Steffen Sledz
2010-06-11 12:38 ` Steffen Sledz
2010-06-14 15:00 ` Henri Bragge
2010-06-14 15:28   ` Steffen Sledz
2010-06-14 16:31     ` henri.bragge
2010-06-15  6:55       ` [PATCH v2] " Steffen Sledz
2010-06-15  7:43         ` Henri Bragge
2010-06-15 16:01           ` John Faith [this message]
2010-06-15 17:59             ` Sledz, Steffen
2010-06-15 11:53         ` Steffen Sledz
2010-06-15 12:49           ` Mike Westerhof

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=4C17A3F3.3000705@soundmetrics.com \
    --to=jfaith@soundmetrics.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.