From Fedora Project Wiki
(Use case format) |
No edit summary |
||
| Line 6: | Line 6: | ||
# Copy the kickstart file to a publicly-accessible place on your HTTP host. | # Copy the kickstart file to a publicly-accessible place on your HTTP host. | ||
# Boot the system and add a <code>ks</code> argument like the following to the boot command line: | # Boot the system and add a <code>ks</code> argument like the following to the boot command line: | ||
#:<pre>ks=http://server.tld/path/to/your/ks.cfg</pre> | #:<pre>ks=http://server.tld/path/to/your/ks.cfg</pre> An example of a kickstart file is:<pre>http://rhe.fedorapeople.org/install/ks.cfg</pre> | ||
|results= | |results= | ||
# The ks.cfg is successfully obtained from the specified location | # The ks.cfg is successfully obtained from the specified location | ||
Revision as of 07:35, 13 July 2010
Description
This test will verify that anaconda can download the requested kickstart file using a HTTP url. It requires a valid kickstart file and a working HTTP host.
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 a publicly-accessible place on your HTTP host.
- Boot the system and add a
ksargument like the following to the boot command line:ks=http://server.tld/path/to/your/ks.cfg
An example of a kickstart file is:http://rhe.fedorapeople.org/install/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