From Fedora Project Wiki
No edit summary |
(Updated for ticket#208) |
||
Line 3: | Line 3: | ||
This test will verify that anaconda can load a kickstart file from a {{filename|file://}} path. This is a typical case for when the kickstart file is located in the {{filename|initrd.img}}. | This test will verify that anaconda can load a kickstart file from a {{filename|file://}} path. This is a typical case for when the kickstart file is located in the {{filename|initrd.img}}. | ||
|actions= | |actions= | ||
<ol> | |||
<li> Prepare a valid kickstart file. For help creating a kickstart file, examine the file {{filename|/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]] | |||
<li> Download the installer initial ramdisk. The ramdisk is typically called {{filename|images/pxeboot/initrd.img}} | |||
<li> Place the kickstart file into the root directory of the installer initial ramdisk using the {{command|pax}} command. For example, | |||
<ol> | |||
<li> Decompress the ramdisk: <pre>xz -c -d initrd.img > initrd.cpio</pre> | |||
{{admon/note|Gzip compressed ramdisk?|Older installer ramdisk images were compressed using [https://secure.wikimedia.org/wikipedia/en/wiki/Gzip gzip] compression. The {{command|file}} command can be used to determine how the ramdisk is compressed. | |||
<pre> | |||
file images/pxeboot/initrd.img | |||
images/pxeboot/initrd.img: gzip compressed data, from Unix, last modified: Thu Oct 21 14:29:08 2010, max compression | |||
</pre> | |||
The {{command|zcat}} command can be used to uncompress gzip compressed ramdisk images. The following example demonstrates decompressing a gzip compressed ramdisk image. | |||
<pre>zcat initrd.img > initrd.cpio</pre>}} | |||
<li> Add the kickstart file: <pre>pax -w -a -f initrd.cpio ks.cfg</pre> | |||
<li> Re-compress the image: <pre>xz --check=crc32 -9 -c initrd.cpio > initrd.img</pre> | |||
{{admon/note|Gzip compressed ramdisk?|As noted earlier, older installer ramdisk images were compressed using [https://secure.wikimedia.org/wikipedia/en/wiki/Gzip gzip] compression. To create a gzip compressed initial ramdisk, use the {{command|gzip}} command as noted below. | |||
<pre>gzip -c initrd.cpio > initrd.img</pre>}} | |||
<li> Boot into the installer using any available means | |||
<li> At the bootloader prompt, provide a location for the kickstart file at the boot prompt. Using the example above: <pre>linux ks=file:///ks.cfg </pre> | |||
</ol> | |||
|results= | |results= | ||
<ol> | <ol> | ||
<li> Confirm the ks.cfg is included in the initial ramdisk. | <li> Confirm the ks.cfg is included in the initial ramdisk. | ||
<pre>xz -c -d initrd.img | cpio -it | grep ks.cfg | |||
ks.cfg </pre> | |||
</li> | </li> | ||
<li> The ks.cfg is | <li> The installer successfully initiates a kickstart install in accordance with the instructions supplied by the {{filename|ks.cfg}} file included in the initial ramdisk. To ensure the kickstart file is properly loaded, inspect the {{filename|anaconda.log}} for a lines similar to the following: | ||
<li> The install should proceed in accordance with the directives in the ks.cfg file</li> | <pre> | ||
15:44:56,189 INFO loader: kernel command line: | |||
15:44:56,189 INFO loader: ks=file:///ks.cfg | |||
... | |||
15:44:59,274 INFO loader: getting kickstart file | |||
15:44:59,274 INFO loader: setting up kickstart | |||
... | |||
15:44:59,906 INFO loader: doing kickstart... setting it up | |||
</pre> | |||
<li> The install should proceed in accordance with the directives in the {{filename|ks.cfg}} file</li> | |||
</ol> | </ol> | ||
}} | }} | ||
[[Category:Kickstart Delivery]] | [[Category:Kickstart Delivery]] |
Revision as of 15:49, 28 June 2011
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.img
.
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,- Decompress the ramdisk:
xz -c -d initrd.img > initrd.cpio
- Add the kickstart file:
pax -w -a -f initrd.cpio ks.cfg
- Re-compress the image:
xz --check=crc32 -9 -c initrd.cpio > initrd.img
- 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.
xz -c -d initrd.img | cpio -it | grep ks.cfg ks.cfg
- The installer successfully initiates a kickstart install in accordance with the instructions supplied by the
ks.cfg
file included in the initial ramdisk. To ensure the kickstart file is properly loaded, inspect theanaconda.log
for a lines similar to the following:15:44:56,189 INFO loader: kernel command line: 15:44:56,189 INFO loader: ks=file:///ks.cfg ... 15:44:59,274 INFO loader: getting kickstart file 15:44:59,274 INFO loader: setting up kickstart ... 15:44:59,906 INFO loader: doing kickstart... setting it up
- The install should proceed in accordance with the directives in the
ks.cfg
file
- Decompress the ramdisk: