Skip to main content

Starting a Kickstart Installation

Firstboot does not run after a system is installed from a Kickstart file unless a desktop and the X Window System were included in the installation and graphical login was enabled. Either specify a user with the user option in the Kickstart file before installing additional systems from it (refer toSection 32.4, “Kickstart Options” for details) or log into the installed system with a virtual console as root and add users with the adduser command.
To begin a kickstart installation, you must boot the system from boot media you have made or the Red Hat Enterprise Linux DVD, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the ks command line argument is passed to the kernel.

DVD and local storage
The linux ks= command also works if the ks.cfg file is located on a vfat or ext2 file system on local storage and you boot from the Red HatEnterprise Linux DVD.

With Driver Disk
If you need to use a driver disk with kickstart, specify the dd option as well. For example, to boot off a boot diskette and use a driver disk, enter the following command at the boot: prompt:
linux ks=hd:partition:/path/ks.cfg dd
If the kickstart file is on a boot CD-ROM as described in Section 32.8.1, “Creating Kickstart Boot Media”, insert the CD-ROM into the system, boot the system, and enter the following command at the boot: prompt (where ks.cfg is the name of the kickstart file):
linux ks=cdrom:/ks.cfg
Other options to start a kickstart installation are as follows:

Do not automatically use the DVD as the install source if we detect a Red Hat Enterprise Linux DVD in your DVD drive.
Make kickstart non-interactive.
Start up pdb immediately.
Use a driver disk.
Sends a custom DHCP vendor class identifier. ISC's dhcpcd can inspect this value using "option vendor-class-identifier".
Comma separated list of nameservers to use for a network installation.
Same as 'dd'.
Turns on special features:
  • allows partitioning of removable media
  • prompts for a driver disk
Gateway to use for a network installation.
Force graphical install. Required to have ftp/http use GUI.
Prompt user for ISA devices configuration.
IP to use for a network installation, use 'dhcp' for DHCP.
Keyboard layout to use. Valid values are those which can be used for the 'keyboard' kickstart command.
The installation program looks for the kickstart file on the NFS server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is and the kickstart file is in the NFS share /mydir/ks.cfg, the correct boot command would be
The installation program looks for the kickstart file on the HTTP server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is and the kickstart file is in the HTTP directory /mydir/ks.cfg, the correct boot command would be ks=
The installation program mounts the file system on <device> (which must be vfat or ext2), and looks for the kickstart configuration file as <file>in that file system (for example, ks=hd:sda3:/mydir/ks.cfg).
The installation program mounts the file system on the specified partition on the specified BIOS device <biosdev>, and looks for the kickstart configuration file specified in <path> (for example, ks=bd:80p3:/mydir/ks.cfg). Note this does not work for BIOS RAID sets.
The installation program tries to read the file <file> from the file system; no mounts are done. This is normally used if the kickstart file is already on the initrd image.
The installation program looks for the kickstart file on CD-ROM, as file <path>.
If ks is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from the "bootServer" from the DHCP response as if it is an NFS server sharing the kickstart file. By default, the bootServer is the same as the DHCP server. The name of the kickstart file is one of the following:
  • If DHCP is specified and the boot file begins with a /, the boot file provided by DHCP is looked for on the NFS server.
  • If DHCP is specified and the boot file begins with something other than a /, the boot file provided by DHCP is looked for in the /kickstartdirectory on the NFS server.
  • If DHCP did not specify a boot file, then the installation program tries to read the file /kickstart/, where is the numeric IP address of the machine being installed.
The installation program uses this network device to connect to the network. For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the commandks=nfs:<server>:/<path> ksdevice=eth1 at the boot: prompt.
Adds HTTP headers to ks=http:// request that can be helpful for provisioning systems. Includes MAC address of all nics in CGI environment variables of the form: "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab".
Language to use for the installation. This should be a language which is valid to be used with the 'lang' kickstart command.
Set the minimum level required for messages to be logged. Values for <level> are debug, info, warning, error, and critical. The default value is info.
Activates loader code to give user option of testing integrity of install source (if an ISO-based method).
Netmask to use for a network installation.
If GUI fails exit.
Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
Do not load support for firewire devices.
Disable IPv6 networking during installation.

This option is not available during PXE installations

During installations from a PXE server, IPv6 networking might become active before anaconda processes the Kickstart file. If so, this option will have no effect during installation.
Don't automatically mount any installed Linux partitions in rescue mode.
Do not auto-probe network devices.
Do not attempt to load support for parallel ports.
Don't pass keyboard/mouse info to stage 2 installer, good for testing keyboard and mouse config screens in stage2 installer during network installs.
Ignore PCMCIA controller in system.
Do not attempt to detect hw, prompts user instead.
Do not put a shell on tty2 during install.
Do not load USB support (helps if install hangs early sometimes).
Do not load usbstorage module in loader. May help with device ordering on SCSI systems.
Do a DVD based installation.
Use <path> for an FTP installation.
Use <path> on <dev> for a hard drive installation.
Use <path> for an HTTP installation.
Use <path> for an NFS installation.
Run rescue environment.
Run installer in mode specified, '1024x768' for example.
Turns on serial console support.
Skips DDC probe of monitor, may help if it's hanging system.
Once installation is up and running, send log messages to the syslog process on <host>, and optionally, on port <port>. Requires the remote syslog process to accept connections (the -r option).
Force text mode install.


If you select text mode for a kickstart installation, make sure that you specify choices for the partitioning, bootloader, and package selection options. These steps are automated in text mode, and anaconda cannot prompt you for missing information. If you do not provide choices for these options, anaconda will stop the installation process.
Prompt for storage device containing updates (bug fixes).
Image containing updates over FTP.
Image containing updates over HTTP.
Don't require an /etc/redhat-release that matches the expected syntax to upgrade.
Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
Once installation is up and running, connect to the vnc client named <host>, and optionally use port <port>.
Requires 'vnc' option to be specified as well.
Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
Requires 'vnc' option to be specified as well.

Popular posts from this blog


The BCD registry file controls which operating system installation starts and how long the boot manager waits before starting Windows. Basically, it’s like the Boot.ini file in earlier versions of Windows. If you need to edit it, the easiest way is to use the Startup And Recovery tool from within Vista. Just follow these steps: 1. Click Start. Right-click Computer, and then click Properties. 2. Click Advanced System Settings. 3. On the Advanced tab, under Startup and Recovery, click Settings. 4. Click the Default Operating System list, and edit other startup settings. Then, click OK. Same as Windows XP, right? But you’re probably not here because you couldn’t find that dialog box. You’re probably here because Windows Vista won’t start. In that case, you shouldn’t even worry about editing the BCD. Just run Startup Repair, and let the tool do what it’s supposed to. If you’re an advanced user, like an IT guy, you might want to edit the BCD file yourself. You can do this

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s

AD LDS – Syncronizing AD LDS with Active Directory

First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N