From Fedora Project Wiki
No edit summary |
(tweaky!) |
||
| Line 4: | Line 4: | ||
# 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]]. | # 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]]. | ||
# Copy the kickstart file to block device for use with this test (e.g. a USB key). For example, you may choose to copy the kickstart file to the {{filename|/boot}} directory which typically resides on the first partition of a disk. | # Copy the kickstart file to block device for use with this test (e.g. a USB key). For example, you may choose to copy the kickstart file to the {{filename|/boot}} directory which typically resides on the first partition of a disk. | ||
# Boot the system from the network install or DVD medium for the release under test and append the following to the boot prompt: <pre>ks=hd:device:path/ks.cfg </pre>. For example, to load a kickstart file called {{filename|ks.cfg}} from the first partition on drive ''sda'', append: <pre>ks=hd:sda1:/ks.cfg</pre> | # Boot the system from the network install or DVD medium for the release under test and append the following to the boot prompt: <pre>inst.ks=hd:device:path/ks.cfg </pre>. For example, to load a kickstart file called {{filename|ks.cfg}} from the first partition on drive ''sda'', append: <pre>inst.ks=hd:sda1:/ks.cfg</pre> | ||
|results= | |results= | ||
# The system should boot from the chosen method and pause at the boot prompt | # The system should boot from the chosen method and pause at the boot prompt | ||
# The entry of <pre>ks=hd:device:path/ks.cfg </pre> should be accepted without error | # The entry of <pre>inst.ks=hd:device:path/ks.cfg </pre> should be accepted without error | ||
# The {{filename|ks.cfg}} file should be read from the specified device/path | # The {{filename|ks.cfg}} file should be read from the specified device/path | ||
# The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file | # The installer should honor the kickstart commands provided in the {{filename|ks.cfg}} file | ||
Revision as of 08:24, 22 November 2012
Description
This test will verify that anaconda mounts and uses a ks.cfg located on a local block device.
How to test
- Prepare a valid kickstart file. For help creating a kickstart file, examine the file
/root/anaconda-ks.cfgon a previously installed system. This file contains the kickstart instructions used to install that system. For additional guidance on kickstart syntax, see Anaconda/Kickstart. - Copy the kickstart file to block device for use with this test (e.g. a USB key). For example, you may choose to copy the kickstart file to the
/bootdirectory which typically resides on the first partition of a disk. - Boot the system from the network install or DVD medium for the release under test and append the following to the boot prompt:
inst.ks=hd:device:path/ks.cfg
. For example, to load a kickstart file calledks.cfgfrom the first partition on drive sda, append:inst.ks=hd:sda1:/ks.cfg
Expected Results
- The system should boot from the chosen method and pause at the boot prompt
- The entry of
inst.ks=hd:device:path/ks.cfg
should be accepted without error - The
ks.cfgfile should be read from the specified device/path - The installer should honor the kickstart commands provided in the
ks.cfgfile - If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.