Specifications

Remote Booting Linux on Intel Processors (CERN Variant)
Concurrent Technologies Page 19 of 30
192.67.84.170:/home/ClientLocalRootFs/client2/etc /etc nfs rw,lock 0 0
5. Upon boot the client will mount the directories specified in the “.fstab.global” and
“.fstab.local” fstab files. The mount points must exist in the RamDisk and any directory in
the existing root file system RamDisk bearing the same name as a mount point will be
mounted over forming the client’s final root file system.
• Make a basic root file system for the first client
“cp -a /etc/ /home/ClientLocalRootFs/client1/”
NOTE: The /etc directory contains many host specific configurations files, and the local
client copies may need editing to suit the individual client needs.
NOTE: Edit the “initdefault” line in “/home/ClientLocalRootFs/client1/etc/inittab” to
read suite the target, is should read either one of the following
id:3:initdefault: # The client will boot into runlevel 3, giving a text login prompt
OR
Id:5:initdefault: # The client will boot into runlevel 5, giving an X login prompt
NOTE: Once the client has booted runlevel services can be configured using the
“chkconfig” administration utility
• Make a common root file system for all clients
“cp -a /usr /home/ClientCommonRootFs”
“cp -a /bin /home/ClientCommonRootFs”
“cp -a /lib /home/ClientCommonRootFs”
“cp -a /sbin /home/ClientCommonRootFs”
• Once the Client is up and running the Client should run the commands in the
“/home/.custom.rc” script. Append the following line to the
“/home/ClientLocalRootFs/client1/etc/rc.d/rc.local” file
/home/.custom.rc
• Update the “home/ClientLocalRootFs/client1/etc/sysconfig/network-scripts/ifcfg-eth0”
file to look like,
DEVICE=eth0
BOOTPROTO=
ONBOOT=no
And update the “home/ClientLocalRootFs/client1/etc/sysconfig/network-scripts/ifcfg-
eth1” file to look like,
DEVICE=eth1
BOOTPROTO=
ONBOOT=no