From Fedora Project Wiki
No edit summary |
m (improve formatting) |
||
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:<pre>ks=http://server.tld/path/to/your/ks.cfg</pre> | # 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> | ||
{{admon/note|You can use the following kickstart for a default installation. Please note that this will erase all your disks. The root password is 'fedora'. <pre>http://mkrizek.fedorapeople.org/default.ks</pre>}} | {{admon/note|Prepared sample kickstart|You can use the following kickstart for a default installation. Please note that this will erase all your disks. The root password is 'fedora'. <pre>http://mkrizek.fedorapeople.org/default.ks</pre>}} | ||
|results= | |results= | ||
# The {{filename|ks.cfg}} is successfully obtained from the specified location | # The {{filename|ks.cfg}} is successfully obtained from the specified location |
Revision as of 15:48, 25 June 2013
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.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 a publicly-accessible place on your HTTP host.
- Boot the system and add a
ks
argument like the following to the boot command line:ks=http://server.tld/path/to/your/ks.cfg
Expected Results
- The
ks.cfg
is successfully obtained from the specified location - The installer should honor the kickstart commands provided in the
ks.cfg
file - If sufficient commands are provided to fully automate an installation, the installer must not prompt for user input.