-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 9 Oct 2009, David Cantrell wrote:
On Sat, 10 Oct 2009, Steffen Maier wrote:
On 10/10/2009 12:27 AM, David Cantrell wrote:
Another catch with DASD is the need for *all* DASD bus IDs to be included
in the dasd= parameter, regardless of whether or not they are used by the
root device.
This is not because of DASD but because there is currently no initscript
that can activate non-root DASDs on boot. That could be repaired and I
think that would be the right solution now that you follow the clean
path for dracutSetupData with DASD in anaconda (instead of my proposed
one-string fits all quick hack).
Let's do the init script then. Should probably be part of the s390utils
package. We'd need to define some sort of control file where anaconda can
write data to telling the init script what DASDs should be activated, but
this
doesn't sound too hard.
This would really simplify things a lot.
On second thought, rather than creating a new init script, we should probably
patch rc.sysinit. Will still need an /etc/sysconfig/dasd file or something
similar that lists the devices to bring online, but the bring up should happen
in rc.sysinit before things are mounted.
- --
David Cantrell <dcantrell@xxxxxxxxxx>
Red Hat / Honolulu, HI
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkrP7oEACgkQ5hsjjIy1VkmCvACcDn++WdKT85XZdF0b2KM2i+hF
iSIAoNomnHKTYGRxkxhwAWlz66oTWw0f
=/sAW
-----END PGP SIGNATURE-----
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
