Well done KP - it looks like that's it!
My previous testing of 3.1-beta2 was with static addresses only, but
I've just built a test machine on my internal network and with stock
3.1-beta2 it won't grab a DHCP address at boot time.
Replacing /bin/busybox in the initrd with a version built from the
latest CVS source (BusyBox 1.8.2 rather than 1.7.3 but still with "#
CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP is not set") gives the same
symptoms.
When I change to "CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP=y" in the
busybox .config and use that version in the initrd it works fine.
Another test is to look at the busybox binary itself (on the build host,
with the "strings" command installed):
With "# CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP is not set" running
"strings busybox | grep dhcpcd" gives no matches.
With "CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP=y" running
"strings busybox | grep dhcpcd" gives:
dhcpcd
dhcpcd -k %iface%
dhcpcd[[ -h %hostname%]][[ -i %vendor%]][[ -I %clientid%]]\
[[ -l % leasetime%]] %iface%
davidMbrooke
On Sat, 2008-01-05 at 02:14 +0100, KP Kirchdoerfer wrote:
> On Saturday 05 January 2008 00:54:50 Mats Erik Andersson wrote:
> > Hello again, Erich and fellow Beringians
> >
> > fre 2008-01-04 klockan 20:59 +0100 skrev Erich Titl:
> > > Mats
> > >
> > > ..., looking at the changelog the first thing that catches my
> > > eye is a new busybox release. Ifup/down are busybox applets, so a new
> > > version might make a difference. Have you tried to step back on busybox?
> >
> > This is a very good point by Erich, it is close to take
> > a daredevil's step to move from Busybox 1.5pre to Busybox 1.7.3
> > when promoting 3.1-beta1 to 3.1-beta2. All the more since
> > I know, after following and sometimes contributing to
> > Busybox myself for a year now, that the ifupdown/dhcpcd
> > code in Busybox needs and mostly gets constant attention,
> > and that those two are closely intertwined in Busybox.
> > If we/you separate Busybox-ifupdown from upstream dhcpcd,
> > the two would most probably need close inspection to function
> > properly. Probably this is what is causing my problems.
> > A first suggestion would be to test Bering-3.1-beta? using
> > Busybox 1.6.1, mostly because that is the point at which
> > I have made the most experience of testing the code for
> > its own sake!
> >
> >
> > Enough of complaints! I will only be able to take time
> > next week in order to build the toolchain for Bering-3.1
> > and at present my toolchain is for Bering-3.0. Thus I leave
> > the endeavour to back step Busybox to test a new floppy
> > image build -- this is what Erich rightfully suggests --
> > to any prospective hero that aspires on sharing the glory
> > with Erich! My teasing is to wet your tongue, no harm
> > ment or taken!
> >
>
> Maybe it is a lot easier - I've overlooked a new feature in .config in latest
> bb source and enable CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP
>
> Anyone able to test a new initrd/image?
>
> kp
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>
> _______________________________________________
> leaf-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/leaf-devel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
