Linux Certif

Toute la documentation sur la certification Linux LPI

ka-d

NAME

ka-d, ka-d.sh - clone this machine with Ka

SYNOPSIS

ka-d.sh -n NUMBER

DESCRIPTION

Ka-d is a script whose goal is to clone the machine where it runs using Ka-deploy. It will mainly read the hard disk partitionning scheme, the way the partitions are mounted, and then use Ka-deploy to clone the machine. The list of the destination nodes is outside the scope of this script, and is managed using the ka_pxe_step script on a tftp server. The NUMBER after the -n switch is the number of clients (i.e destination nodes) that the ka-d-server program will wait before starting the transfers. Since this script acts as a 'cloning server' it will be referred to as 'server' in the rest of this document.

OPTIONS

-m drive

Copy the master boot record of the specified drive on the same drive on the remote machine. drive can be under the form hda or /dev/hda.

-M drive file

Same as above, but use the given file as boot record.

-d NUM

Normally the server will send an 'exit signal' to the clients when they have all received the data. If this option is enabled, the server will introduce a delay between the release of the clients. This delay is the given number in tenths of second. We use this option to smooth the load on our TFTP servers for whole-cluster system installations.

-x dir

Do not send the contents of the given directory. Typical use would be -x /tmp for instance.

-D partition

Also send to the clients the given partition. This one should be given under the form /dev/foo. The partition will be read, sent and written as raw binary data. This can be used for windows partitions for instance.

-p drive file

Do not copy the partition table of drive, but use the given partition description file instead. Use this when the source and destination nodes are not exactly identical.

-r command

Run command on the destination nodes after cloning. Typical use would be -r lilo for instance.

PARTITION TABLE DESCRIPTION

The files used with the -p option must have this form: One line per partition, with two fields : type of partition and size in megabytes. The type can be linux, swap, extended. Other types can be obtained by appending their hexadecimal number to 'type'. For example linux is the same as type83. The size is either a number of megabytes, or the keyword fill (to take all available space). The logical partitions must have the logical keyword.

Example:

 
 # hda1 = linux root
 linux 5000
 # hda2 = swap
 swap 300
 # hda3 = extended
 extended fill
 # hda5 and 6 = linux
 logical linux 500
 logical linux fill
 

This description scheme will not work for complicated partition tables but should be OK most of the time.