Created attachment 100380 [details]
sample hardware.conf with included s390/s390x documentation

The alternative is if we can find any particular way to determine if
these are available, dmesg, ifconfig -a, /proc/scsi/scsi etc.  we
could add them to discovery instead.

For the network devices, this awk scriptlet should list the available
devices:

$ awk ' /Initialised Devices/,/Total device memory usage/ '
/proc/chandev | awk ' (NF==14)&&($1 !~ /irq/) { print $10;}'
eth0
eth1
ctc0
hsi2
$

please add this to discovery phase, then network devices should be
automatically detected ... an /etc/sysconfig/network-scripts/ifcfg-*
entry for each interface will  still be needed in advance of testing ...

any chance redhat-config-network can at least create those without
requireing the user to type them in by hand.  In theory it should work
even if it doesn't know about these "fancy" devices.

redhat-config-network is not able to create these devices (billgo has
already filed bug) ... this won't be corrected until U3 (at least) and
so won't help us for U2 validation ...

ah; oh well

Adding the dasd and scsi scriptlets

$ awk '/active at blocksize/ { print $7; } '  /proc/dasd/devices
<borgan> this snippet will get you your dasd list

<borgan> $ dmesg | awk ' /SCSI device/ { print $3;} ' | awk ' BEGIN
{FS=":";} { print $1; } '
<borgan> this should get you scsi disk

Should be resolved in 0.9-14.2 or higher