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

The second change would be the bootloader, for a DHCP based network, ip=dhcp will need to be added to kernel line.
Grub would look like

cat > ${CLFS}/boot/grub/menu.lst << "EOF"
# Begin /boot/grub/menu.lst

# By default boot the first menu entry.
default 0

# Allow 30 seconds before booting the default.
timeout 30

# Use prettier colors.
color green/black light-green/black

# The first entry is for CLFS.
title CLFS SVN-20060911
root (hd0,3)
kernel /boot/clfskernel-2.6.17.13 root=/dev/hda4 ip=dhcp
EOF

For Static IP's, ip=parameters will need to be added to the kernel line

cat > ${CLFS}/boot/grub/menu.lst << "EOF"
# Begin /boot/grub/menu.lst

# By default boot the first menu entry.
default 0

# Allow 30 seconds before booting the default.
timeout 30

# Use prettier colors.
color green/black light-green/black

# The first entry is for CLFS.
title CLFS SVN-20060911
root (hd0,3)
kernel /boot/clfskernel-2.6.17.13 root=/dev/hda4 
ip=192.168.1.1::192.168.1.254:255.255.255.0:clfs
EOF


The final change will be adding inetutils to the boot build order.

Please comment via this thread.
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev

Reply via email to