User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.10) Gecko/20100506 SUSE/3.5.10-0.1 Firefox/3.5.10

As suggested by Lee Duncan (see bug 630434 comment 42 and 44), I am creating this bug to keep track of the suggested inclusion of a template file named "/etc/sysconfig/initrd" for "mkinitrd".

This template can then be used to configure speciel system setups like having the root device using another path than what "mkinitrd" is capable to figure out ("mkinitrd" does in certain corner cases come up with a wrong path name to the actually used root device), or to handle the special case, where e.g. "/home" is on an iSCSI device, but all other file systems (especially including the root device) are on local disks.
In this case the iSCSI device holding "/home" would have been configured with a start up parameter == "onboot", but "mkinitrd" would *not* include the iSCSI stack in the "initrd", while the root file system is not on an iSCSI device, thus effectively causing the system from being able to boot up, while the "/home" file system is missing.

Using the "/etc/sysconfig/initrd" template and setting the "root_iscsi=1" variable in here, it is possible to force the inclusion of the iSCSI stack to be included in the "initrd" file, thus allowing for the attachment of the iSCSI device holding the "/home" file system.

Reproducible: Always

Steps to Reproduce:
Steps on how to reproduce the root course this template fixes, please, refer to bug 630434.
Actual Results:  
Refer to bug 630434.

Expected Results:  
Refer to bug 630434.