From Fedora Project Wiki
m (typo) |
No edit summary |
||
| Line 2: | Line 2: | ||
|description=Test the non-interactive ''cmdline'' output mode. This mode simply prints out text and does not allow any interactivity. All options must be specified either in a kickstart file or on the command line. | |description=Test the non-interactive ''cmdline'' output mode. This mode simply prints out text and does not allow any interactivity. All options must be specified either in a kickstart file or on the command line. | ||
|actions= | |actions= | ||
# Prepare a | # 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]]. | ||
# Boot the installer with the command-line option ''cmdline'' | # Boot the installer with the command-line option ''cmdline'' as well as <code>ks</code> argument to load the kickstart file | ||
|results= | |results= | ||
# Anaconda completes successfully | # Anaconda completes successfully | ||
Revision as of 07:50, 30 June 2010
Description
Test the non-interactive cmdline output mode. This mode simply prints out text and does not allow any interactivity. All options must be specified either in a kickstart file or on the command line.
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. - Boot the installer with the command-line option cmdline as well as
ksargument to load the kickstart file
Expected Results
- Anaconda completes successfully
- Anaconda does not stop and prompt for user input
- Reboot successfully into installed system