Installation guide

nochroot:
This command is available in Red Hat Enterprise Linux 5.5 and later.
%post --log=/root/ks-post.log
with --nochroot:
%post --nochroot --log=/mnt/sysimage/root/ks-post.log
31.7.1. Examples
Register the system to a Subscription Asset Manager server, using the --log option to log the result
(in Red Hat Enterprise Linux 5.5 and later):
%post --log=/root/ks-post.log
/usr/sbin/subscription-manager register --username=[e-mail] --
password=secret --serverurl=sam-server.example.com --org="Admin Group" --
environment="Dev" --servicelevel=standard
Run a script named runme from an NFS share:
mkdir /mnt/temp
mount -o nolock 10.10.0.2:/usr/new-machines /mnt/temp open -s -w --
/mnt/temp/runme
umount /mnt/temp
Note
NFS file locking is not supported while in kickstart mode, therefore -o nolock is required
when mounting an NFS mount.
31.8. Making t he Kickst art File Available
A kickstart file must be placed in one of the following locations:
On a boot diskette
On a boot CD-ROM
On a network
Normally a kickstart file is copied to the boot diskette, or made available on the network. The network-
based approach is most commonly used, as most kickstart installations tend to be performed on
networked computers.
Let us take a more in-depth look at where the kickstart file may be placed.
31.8.1. Creat ing Kickst art Boot Media
Diskette-based booting is no longer supported in Red Hat Enterprise Linux. Installations must use
CD-ROM or flash memory products for booting. However, the kickstart file may still reside on a
diskette's top-level directory, and must be named ks.cfg.
Red Hat Ent erprise Linux 5 Inst allat ion G uide
310