Specifications

Remote Booting Linux on Intel Processors (CERN Variant)
Concurrent Technologies Page 13 of 30
mknod ttyS4 c 4 68
echo Done.
3. Creating the binary directories. Instead of the using the standard binary files in our RamDisk,
as we did for the NFS example above, we will use a set of binaries that have been optimised
for embedded systems. The standard set of binaries will occupy a good few megabytes of
disk space. However, the optimised versions will occupy a mere few hundred kilobytes.
• Download the latest version of BusyBox from
http://www.busybox.net The BusyBox
program contains the BusyBox binary that implements many of the standard binaries,
optimised on space and functionality, but still providing a very useful system.
• Copy the BusyBox file to the BusyBox directory and unpack it,
“mkdir /root/BusyBox”
“cd /root/BusyBox”
“cp <path to busybox-0.60.5.tar.gz>/busybox-0.60.5.tar.gz .”
“gzip -d busybox-0.60.5.tar.gz” #Uncompress the tar file
“tar -xf busybox-0.60.5.tar” #Un-tar the file
4. Compile and install the BusyBox functions into the RamDisk directory. The BusyBox
program is configured with a simple “Config.h” file in its root directory. The default setting
provide most of the routine functionality of a Linux system, although the “ifconfig” function
is not included by default and so needs to be included, and also the “Ping” function is not
included by default, which might be useful,
• cd “/root/BusyBox/busybox-0.60.5”
• In “Config.h”, edit and modify the “//#define BB_IFCONFIG” line to “#define
BB_IFCONFIG”. This will include the ifconfig command into BusyBox. Edit and
modify the “//#define BB_FEATURE_IFCONFIG_STATUS” line to “//#define
BB_FEATURE_IFCONFIG_STATUS”. This will include the ifconfig status features
into BusyBox. . Edit and modify the “//#define BB_FEATURE_MTAB_SUPPORT”
line to “#define BB_FEATURE_MTAB_SUPPORT”. This will include support for
“/etc/mtab”. Edit and modify the “//#define BB_ROUTE” line to “//#define
BB_ROUTE”. Edit and modify the “//#define BB_PING” line to “#define BB_PING”.
This will include the ping command into BusyBox. Have a look around the “Config.h”
file and customise as necessary.
• Make and install the BusyBox files into the RamDisk directory,
“make PREFIX=/tftpboot/RamDiskFs install”
5. Instead of hard-coding the Ethernet configuration in our RamDisk, as we did for the NFS
example above, we will use DHCP client to obtain the details from the DHCP server. This
configuration will allow the same RamDisk to be served to multiple clients. We will use an
optimised DHCP client from BusyBox.
• Download the latest version of BusyBox UDHCP software from
http://udhcp.busybox.net
• Copy the UDHCP software file to the BusyBox directory and unpack it,
“cd /root/BusyBox”
“cp <path to udhcp-0.9.8.tar.gz>/udhcpd-0.9.8.tar.gz .”
“gzip -d udhcp-0.9.8.tar.gz” #Uncompress the tar file
“tar -xf udhcp-0.9.8.tar” #Un-tar the file
6. Compile and install the UDHCP functions into the RamDisk directory.