Installation guide

Chapter 1. Kickstart Installations 41
ks=hd: device / file
The installation program will mount the filesystem on device (which must be vfat
or ext2), and look for the kickstart configuration file as
file in that filesystem (for
example, ks=hd:sda3/mydir/ks.cfg).
ks=file:/
file
The installation program will try to read the file file from the filesystem; no
mounts will be done. This is normally used if the kickstart file is already on the initrd
image.
ks=cdrom:/
path
The installation program will look for the kickstart file on CD-ROM, as file path .
ks
If ks is used alone, the installation program will configure the Ethernet card in the sys-
tem using DHCP. The system will use the "bootServer" from the DHCP response as an
NFS server to read the kickstart file from (by default, this is the same as the DHCP
server). The name of the kickstart file is one of the following:
• If DHCP is specified and the bootfile begins with a /, the bootfile provided by DHCP
is looked for on the NFS server.
• If DHCP is specified and the bootfile begins with something other then a /, the boot-
file provided by DHCP is looked for in the /kickstart directory on the NFS server.
• If DHCP did not specify a bootfile, then the installation program tries to read the file
/kickstart/1.2.3.4-kickstart, where 1.2.3.4 is the numeric IP address of the
machine being installed.
ksdevice=
device
The installation program will use this network device to connect to the network.
For example, to start a kickstart installation with the kickstart file on an NFS
server that is connected to the system through the eth1 device, use the command
ks=nfs:
server: / path ksdevice=eth1 at the boot: prompt.