Revision as of 10:10, 11 July 2011

Description

This test will verify that anaconda mounts and uses a ks.cfg located on a local block device.

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 block device for use with this test (e.g. a USB key). For example, you may choose to copy the kickstart file to the /boot directory which typically resides on the first partition of a disk.
Boot the system and enter the following at the boot prompt
```
linux ks=hd:device:path/ks.cfg 
```
. For example, to load a kickstart file called ks.cfg from the first partition on drive sda, type:
```
linux ks=hd:sda1:/ks.cfg
```

The system should boot from the chosen method and pause at the boot prompt
The entry of
```
linux ks=hd:device:path/ks.cfg 
```
should be accepted without error
The {{filename}ks.cfg}} file should be read from the specified device/path
The install should proceed in accordance with the directives in the ks.cfg file
Anaconda should not prompt for user interaction if ks.cfg is not specified

@@ Line 8: / Line 8: @@
 # The system should boot from the chosen method and pause at the boot prompt
 # The entry of <pre>linux ks=hd:device:path/ks.cfg </pre> should be accepted without error
-# The 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 install should proceed in accordance with the directives in the ks.cfg file
+# Anaconda should not prompt for user interaction if {{filename|ks.cfg}} is not specified
 }}
 [[Category:Kickstart Delivery]]