cmd:kickstart

Prev		Next

RedHat Linux comes with a feature called KickStart. This feature lets you automate most/all of a RedHat Linux installation.

It lets you create a single file (ks.cfg) which contains the answers the all the questions that would normally be asked during a typical RedHat Linux installation.

It does standardized installations, but also can tolerate a certain amount of hardware differences: e.g., NIC, Video, Hard drive sizes, etc.

Kickstart Simple Install

All the kickstart howtos/documents throw too much detail information to me. You get frustrated very quickly: "kickstart should be simple, why there is no simple explaination for a simple task?". Now, here is the simplest way you can make use of kickstart feature:

Prepare a kickstart config file

Use the command ksconfig to produce one. It will help you understand what those lines mean. Hint: use the "save file…" often, to preview the result.
Merge in whatever you think valuable from \root\anaconda-ks.cfg. This is how your current Linux is installed.

Go for it

Copy it to any MS-DOS floppy, naming it "ks.cfg". Yes! any DOS disk will do, not necessarily a Linux Boot disk!

Then, boot off your RH cdrom. At syslinux boot prompt type:

linux ks=floppy

That's it. Vola!

Advanced usage

Prepare as many kickstart config files as you want, store them all in one floppy disk. Hand pick one that is most suitable for your installation situation. Suppose I name my fully automatic lab installation kickstart config file (that automatically partition and install Linux on the system) as ks-lab1.cfg. At boot prompt type:

linux ks=hd:fd0/labs/ks-lab1.cfg

Then go for a sip of coffee, everything would be in perfect shape when you return.

Note, you can only put kickstart config files on floppy disk if you are not booting from it. Otherwise, you'll get an error saying kickstart file not found. (Tested on RH7.3, as of 2002.08.29 Thu)

If you are booting from floppy, copy the kickstart config files to your hard disk, then issues the following:

linux ks=hd:hda1/rh73/ks1.cfg

ksconfig usage help

If you are happy with your choices, click the Save File button within the dialog box. A save file dialog box will appear and allow you to choose where to save the file. The default file name to save it as is ks.cfg. Copy the kickstart file (ks.cfg) on a floppy disk.

Boot from the disk and type linux ks=floppy to start the kickstart installation. To learn about different methods for starting a kickstart installation refer to the Official Red Hat Linux Customization Guide.

partition handling sample

Use existing

clearpart --linux
part / --fstype ext3 --onpart hda3
part swap --onpart hda2
part /export --fstype ext3 --onpart hda4

create

clearpart --linux
part swap --size=384 --asprimary
part / --fstype ext3 --size=2200 --asprimary
part /export --fstype ext3 --size=1 --grow --asprimary

Helpful tip

Best approach

Normally it would take many time of try-and-errors before you can have a good and working copy of ks.cfg. To make things easier, do not burn and cd when trying. Otherwise, it is a waste of time and your cd. Install from hard drive images instead!

Alternate Consoles

A lot of information is made available during the installation process on alternate consoles. Press ALT and a function key to switch to a different console. This is especially useful if the installation fails. E.g., a kickstart installation will fail if a package in the list of those to install is not available. If it does happen, at least you can get more detailed error messages this way, or even a shell.

Console 1 (ALT-F1): graphical installation status (what's normally shown during installation).

Console 2 (ALT-F2): bash shell (once the installation has progressed far enough).

Console 3 (ALT-F3): Installation progress log, including module insertion. The cause of an error can often be found here.

Console 4 (ALT-F4): Appears to be a log of raw device/SCSI information.

Console 5 (ALT-F5): Appears to be a log of filesystem operations.