Subtitles of the Movie

This video will demonstrate an automated Kickstart installation, at least the start of it. Once configured, as done in another video, automated Kickstart installations are fairly simple. All you need to do is include the desired Kickstart file on an appropriate device, and start the installation process. We assume the installation is done over a network server so you don't have to change CDs. Let's start the Red Hat Enterprise Linux 5 installation process. When you get to the initial installation screen you need to know how to call the Kickstart file from appropriate media. For example, if I've set up the Kickstart file on a USB key I could cite it with a command such as ks for Kickstart, the Kickstart file being on a hard drive of some sort, on some USB device on the first partition. Some trial and error may be required. And since I've put the Kickstart file on the top level directory on that USB key I would just cite that file name after a forward slash. And I'd just cite the name of the Kickstart file, which I've arbitrarily named ks dot cfg. Sometimes administrators will set up the Kickstart file on the same CD that they use to boot and start the installation program. It's available on the boot dot iso file described in the RHCT course. If that's what's been done just say it starts from the local CD ROM and let's say I've put the ks dot cfg file on the top level directory on that CD ROM. The final option we'll actually test out is, with the Kickstart file on the local floppy drive. The first floppy drive most commonly is associated with the devfd0 device. If I put it on the top level directory of the floppy I cited it as follows. And the installation process starts normally. We'll see in a moment that it actually goes through the installation screens automatically because it takes the input that you've put into the Kickstart file. Right now, if you didn't have a Kickstart file you'd be expecting to put in things like keyboard and language but the Kickstart file proceeds on its own. The directives in the file are automatically fed to the installation program. If there's an error in the Kickstart file or insufficient information, it'll stop and request your input. And that's not necessarily a bad thing. It allows you to test an automated installation before rolling it out on a substantial number of computers.