From Fedora Project Wiki

m (Added category)
m (fix numbering)
Line 6: Line 6:
== Steps To Reproduce ==
== Steps To Reproduce ==


1.  Prepare a valid kickstart file and copy to the device and path to be used for the test (i.e. usb key).
# 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>
1.  Boot the system and enter the following at the boot prompt
 
<code>linux ks=hd:device:path/ks.cfg </code>




Example:
Example:


<code>linux ks=hd:sda1:/mydir/ks.cfg</code>
<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
1. 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
1. The entry of
# The install should proceed in accordance with the directives in the ks.cfg file
<code>linux ks=hd:device:path/ks.cfg </code>
should be accepted without error
 
1. The ks.cfg file should be read from the specified device/path
 
1. The install should proceed in accordance with the directives in the ks.cfg file


[[Category:Installer Test Cases|KickstartKsHdDevicePathKsCfg]]
[[Category:Installer Test Cases|KickstartKsHdDevicePathKsCfg]]

Revision as of 15:01, 16 July 2008

KickstartKsHdDevicePathKsCfg

Description

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


Steps To Reproduce

  1. Prepare a valid kickstart file and copy to the device and path to be used for the test (i.e. usb key).
  2. Boot the system and enter the following at the boot prompt
    linux ks=hd:device:path/ks.cfg 


Example:

linux ks=hd:sda1:/mydir/ks.cfg


Expected Results

  1. The system should boot from the chosen method and pause at the boot prompt
  2. The entry of
    linux ks=hd:device:path/ks.cfg 
    should be accepted without error
  3. The ks.cfg file should be read from the specified device/path
  4. The install should proceed in accordance with the directives in the ks.cfg file