All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Westerhof <mike@mwester.net>
To: 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 07:49:50 -0500	[thread overview]
Message-ID: <4C1776EE.3080206@mwester.net> (raw)
In-Reply-To: <4C1769D5.4020601@dresearch.de>

Steffen Sledz wrote:
> Am 15.06.2010 08:55, schrieb Steffen Sledz:
>> * 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.
> 
> Some more ACKs?
> 
> Or NAKs (i hope not)?

I shall test with SlugOS, but that's a huge task -- not because of this
change, but because since the sysroot change many weeks ago, we still
have not got SlugOS building in OE again.  With the help of Khem, we're
a lot closer (gcc 4.2.4 builds again), but I still can't generate a
working LE image.

I'll see if I can get a BE image to work well enough today to test this.

-Mike



      reply	other threads:[~2010-06-15 13:01 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
2010-06-15 17:59             ` Sledz, Steffen
2010-06-15 11:53         ` Steffen Sledz
2010-06-15 12:49           ` Mike Westerhof [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=4C1776EE.3080206@mwester.net \
    --to=mike@mwester.net \
    --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.