From Fedora Project Wiki
(add a expected result to check install process runs unattended(ticket#217)) |
(Updated for F16-style images) |
||
Line 6: | Line 6: | ||
<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> 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> 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| | <li> Place the kickstart file into the root directory of the installer initial ramdisk using the {{command|cpio}} command. <pre>echo ks.cfg | cpio -c -o >> initrd.img</pre> | ||
<li> Boot into the installer kernel ({{filename|vmlinuz}}) and the modified initial ramdisk ({{filename|initrd.img}}) using any available means | |||
</pre> | |||
{{ | |||
<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> | <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> | </ol> | ||
|results= | |results= | ||
<ol> | <ol> | ||
<li> Confirm the ks.cfg is included in the initial ramdisk. | <li> Confirm the {{filename|ks.cfg}} is included in the initial ramdisk. The user-space commands to inspect the Fedora 16 initrd.img contents are not yet available. The only way to ensure the provided {{filename|ks.cfg}} is used is to boot the installer | ||
<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 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: | ||
<pre> | <pre> |
Revision as of 20:50, 25 July 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
cpio
command.echo ks.cfg | cpio -c -o >> initrd.img
- Boot into the installer kernel (
vmlinuz
) and the modified initial ramdisk (initrd.img
) 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. The user-space commands to inspect the Fedora 16 initrd.img contents are not yet available. The only way to ensure the providedks.cfg
is used is to boot the installer - 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 - Anaconda should not prompt for user interaction if
ks.cfg
is not specified