From Fedora Project Wiki
(Unify the kickstart case steps) |
mNo edit summary |
||
Line 13: | Line 13: | ||
|results= | |results= | ||
# Confirm the ks.cfg is included in the initial ramdisk. | # Confirm the ks.cfg is included in the initial ramdisk. | ||
#: <pre>zcat | #: <pre>zcat initrd.img | pax | grep ks.cfg | ||
#: ks.cfg </pre> | #: ks.cfg </pre> | ||
# The ks.cfg is successfully obtained from the specified location | # The ks.cfg is successfully obtained from the specified location |
Revision as of 20:49, 23 October 2010
Description
This test will verify that anaconda can load a kickstart file from a file:// path. This is a typical case for when the kickstart file is located in the initrd or stage#1 environment.
How to test
- Prepare a valid kickstart file. For help creating a kickstart file, examine the file
/root/anaconda-ks.cfg
on a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see Anaconda/Kickstart. - Download the installer initial ramdisk. The ramdisk is typically called
images/pxeboot/initrd.img
. - Place the kickstart file into the root directory of the installer initial ramdisk using the
pax
command. For example,- Untar the ramdisk:
zcat initrd.img > initrd.cpio
- Add the kickstart file:
pax -w -a -f initrd.cpio ks.cfg
- Compress the image:
gzip -c initrd.cpio > initrd.img
- Untar the ramdisk:
- Boot into the installer using any available means
- At the bootloader prompt, provide a location for the kickstart file at the boot prompt. Using the example above:
linux ks=file:///ks.cfg
Expected Results
- Confirm the ks.cfg is included in the initial ramdisk.
zcat initrd.img | pax | grep ks.cfg
- ks.cfg
- The ks.cfg is successfully obtained from the specified location
- The install should proceed in accordance with the directives in the ks.cfg file