Revision as of 14:09, 30 January 2009

Description

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

Prepare a valid kickstart file and copy to the device and path to be used for the test (i.e. usb key).
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 /mydir/ks.cfg from the first partition on drive sda, type:
```
linux ks=hd:sda1:/mydir/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 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

@@ Line 1: / Line 1: @@
-= KickstartKsHdDevicePathKsCfg =
+= Description =
-== Description ==
 This test will verify that anaconda mounts and uses a ks.cfg located on the defined device.
+= Steps To Reproduce =
-== Steps To Reproduce ==
 # Prepare a valid kickstart file and copy to the device and path to be used for the test (i.e. usb key).
-# Boot the system and enter the following at the boot prompt <pre>linux ks=hd:device:path/ks.cfg </pre>
+# Boot the system and enter the following at the boot prompt <pre>linux ks=hd:device:path/ks.cfg </pre>.  For example, to load a kickstart file called ''/mydir/ks.cfg'' from the first partition on drive ''sda'', type: <pre>linux ks=hd:sda1:/mydir/ks.cfg</pre>
-Example:
-<pre>linux ks=hd:sda1:/mydir/ks.cfg</pre>
-== Expected Results ==
+= Expected Results =
 # 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
@@ Line 22: / Line 12: @@
 # The install should proceed in accordance with the directives in the ks.cfg file
-[[Category:Installer Test Cases|KickstartKsHdDevicePathKsCfg]]
+[[Category:Kickstart Delivery]]