Jim Gifford wrote: > The development team has been talking, and a few people have expressed > some concerns with the boot build method. A lot of people think it > should be a fully functional system, with the ability to use the > network. Which everyone agree's needs to happen, but everyone has a > different idea. This is to propose the idea I think will benefit > everyone, will only 1 package added to the build. > > My proposal is to add IP Kernel Autoconfiguration to the kernel build > in the boot build section. I have tested this numerous times with > netboot and boot style builds. The change would require a few items > selected in the kernel at build time. Also at least one network driver > will also need to be selected during the build along with these options. > > Device Drivers ---> > Networking support ---> > Networking options ---> > [*] IP: kernel level autoconfiguration > [*] IP: DHCP support > [*] IP: BOOTP support > [*] IP: RARP support Same here, every sparc or mips build I do is a netboot. I've never had a problem with the kernel configuration. > > The second change would be the bootloader, for a DHCP based network, > ip=dhcp will need to be added to kernel line. > > kernel /boot/clfskernel-2.6.17.13 root=/dev/hda4 ip=dhcp > > For Static IP's, ip=parameters will need to be added to the kernel line > > kernel /boot/clfskernel-2.6.17.13 root=/dev/hda4 > ip=192.168.1.1::192.168.1.254:255.255.255.0:clfs > >From Documentation/nfsroot.txt in the kernel docs. ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf> > > The final change will be adding inetutils to the boot build order. > I've never installed inetutils for any of the times I've netbooted a system. Any specific reason why? It doesn't bother me to build it, Just curious why.
_______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
