Two methods for creating the required Kickstart configuration file:

cat /root/anaconda-ks.cfg

ksconfig command (GUI: Main Menu | System Tools | Kickstart)

Creating a floppy:

edit the anaconda-ks.cfg

mount /mnt/floppy

dd if=/mnt/cdrom/images/bootdisk.img of=/dev/fd0

cp /root/anaconda-ks.cfg /mnt/floppy/ks.cfg

vi /mnt/floppy/ks.cfg

If you don't see it --> not enough room? rm snake.msg

to delete the description of options? general.msg, options.msg, param.msg, and rescue.msg

boot -> boot: linux ks=floppy

Kickstart with DHCP: (Doesn't come on the exam cuz of a bug)

vi /etc/dhcpd.conf

filename “/usr/install/”

next-server servername

Starting the Installation with a Kickstart File

boot: linux ks=floppy (Boot from Floppy)

boot: linux ks=hd:fd0:/ks.cfg (Boot from CD to read from Floppy)

boot: linux ks=hd:hda2:/home/mj/ks.cfg (refer to the Kickstart configuration file on a hard disk)

boot: linux ks=nfs:192.168.17.18:/kicks/ks.cfg (To boot from an NFS server)

boot: linux ks=http:192.168.17.18:/kicks/ks.cfg (To boot from an HTTP server)

Kickstart Partitioning

clearpart --all [clear all partitions]

clearpart --linux [clear any Linux-type partitions]

part mount dir --size size [--grow] [--maxsize size]

The size is in megabytes.

--grow option to allow the partition to expand and fill all remaining disk space after fixed-size partitions are added.

--maxsize, which will allow the partition to grow only to the size specified in megabytes.

clearpart --all --drives=hda

part /boot --fstype ext3 --size=100 --ondisk=hda

part / --fstype ext3 --size=1024 --grow --ondisk=hda

part swap --size=256 --grow --maxsize=512 --ondisk=hda