From Fedora Project Wiki
m (Added category) |
m (fix numbering) |
||
| Line 7: | Line 7: | ||
# Prepare a valid kickstart file and copy to a on disk location accessible by the stage#1 loader. This is typically copied inside the initrd used for the installation. | |||
# Boot the system and enter the following at the boot prompt <pre>linux ks=file://path/ks.cfg </pre> | |||
< | |||
Example: | Example: | ||
<pre>linux ks=file:/etc/ks.cfg</pre> | |||
< | |||
== Expected Results == | == Expected Results == | ||
# The ks.cfg is successfully obtained from the specified location | |||
# The install should proceed in accordance with the directives in the ks.cfg file | |||
[[Category:Installer Test Cases|KickstartKsFilePathKsCfg]] | [[Category:Installer Test Cases|KickstartKsFilePathKsCfg]] | ||
Revision as of 15:00, 16 July 2008
KickstartKsFilePathKsCfg
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.
Steps To Reproduce
- Prepare a valid kickstart file and copy to a on disk location accessible by the stage#1 loader. This is typically copied inside the initrd used for the installation.
- Boot the system and enter the following at the boot prompt
linux ks=file://path/ks.cfg
Example:
linux ks=file:/etc/ks.cfg
Expected Results
- The ks.cfg is successfully obtained from the specified location
- The install should proceed in accordance with the directives in the ks.cfg file