KICK START INSTALLTION

From Server

# cd /etc

# cp anaconda-ks.cfg ks.cfg

Note : goto X window system, select System tools – KICKSTART. Modify basic configuration installation method

NFS ip address : 192.168.10.1,  Directory : /var/ftp/pub

Network : DHCP

Select the way you want to do (for Select language, keyboard layout, partition, packages, boot loader etc.,)

Above information save the file to ks.cfg

Kick start installations possibility on four ways 1. FLOPPY 2.NFS 3.FTP 4.HTTP

# mount /media/floppy

# cp ks.cfg /media/floppy

# umount /media/floppy

To Client

Note : Put the Linux cd1 from the client machine and boot.  Follow the any one command with your

          choice of installations

# linux ks=floppy

# linux ks=nfs:192.168.0.254:/kicks/ks.cfg   (kicks – This is a directory which contains  ks.cfg file)

# linux ks=ftp:192.168.0.254:/kicksftp/ks.cfg cfg   (kicksftp – This is a directory which contains ks.cfg file)

# linux ks=http:192.168.0.254:/kickshttp/ks.cfg cfg   (kickshttp – This is a directory which stores in ks.cfg file)

Installation starting

Kickstart

 Overview  

Kickstart provides a way to do automated installations.

The Kickstart configuration file (ks.cfg) answers all the questions that are normally asked during a normal install.

Allows you to automate most of the installation, including the following:

·         Language Selection

·         Mouse Configuration

·         Keyboard Selection/Configuration

·         Boot Loader Installation

·         Disk Partitioning

·         Network Configuration

·         Authentication (NIS, LDAP,Kerberos, Samba, and Hesoid)

·         Firewall Configuration

·         X Window System Configuration

·         Package Selection

Packages

·         mkkickstart - This package provides utilities that will create a kickstart file based on the current machine's configuration.

·         ksconfig - Provides a graphical interface for creating kickstart files.

 Creating a Kickstart File

Manual

Copy the sample.ks kickstart file from the RH-DOCS directory on the documentation CD and modify it to meet your requirements. Be careful when editing it because the sections must remain in order. The order is:

·         Command Section

·         %package Section

·         %pre & %post Sections

mkkickstart

Use the mkkickstart utility to create a kickstart configuration file based on the current system's configuration.

ksconfig

Use the GUI tool ksconfig to create a kickstart file.

 Kickstart Installation Types

Network

·         Requires a DHCP/BOOTP server.

·         ks.cfg file must be accessible from NFS, FTP, HTTP, or Samba (although I've only been able to get it to work when the ks.cfg file is on NFS).

·         Can install from NFS, FTP, HTTP, & Samba.

Local

·         ks.cfg file must be put on a floppy boot disk.

·         Can install from a local CD-ROM or a local hard drive.

 Kickstart Installation

Boot with a boot floppy. For a local kickstart installation, the ks.cfg must be located in the root of the boot disk.

When SYSLINUX installation screen comes up, specify one of the following options:

·         ks=floppy - If ks.cfg is located on the floppy.

·         ks=hd:fd0/ks.cfg - Same as ks=floppy above.

·         ks=floppy dd - When ks.cfg is located on the floppy and you need a driver disk.

·         ks=nfs::/path - ks.cfg file is on an NFS server.

·         ks=http::/path - ks.cfg file is on an HTTP server.

·         ks=ftp::/path - ks.cfg file is on an FTP server.

 Additional Network Installation Info

When specifying "linux ks" at the installation prompt:

·         The ks.cfg file must be available via NFS.

·         By default, it is assumed that the ks.cfg file will be on the same server as the DHCP/BOOTP server. To specify a different server for the ks.cfg file, specify the following in the /etc/dhcpd.conf file:

filename "/path/to/ks.cfg"

next-server

       

If the path specified in the "filename" clause ends with a "/", then the file that is looked for is: "/specified/path/-kickstart" where is the IP address of the machine making the request.

Note that the path specified in the "filename" clause must be the full path to the file and not the relative path from the NFS export. Kickstart will automatically try to mount the NFS export based on the path's name. In the above example, it would first try to mount "/path", then if that failed, "/path/to".

If you don't wish to use DHCP to specify the location of the kickstart file, you can specify one of the options listed above to point to the location of the ks.cfg file.

To install from NFS, the following directive must be used in the ks.cfg file right after the "install" directive:

nfs --server --dir

To install from HTTP or FTP, the following directive must be used in the ks.cfg file right after the "install" directive:

url --url http:///path

url --url ftp:///path