Jeremy Katz wrote:
On Wed, 2008-01-30 at 20:58 +0100, Joel Andres Granados wrote:
In anaconda, when it is time to write the mdadm.conf file, it is done by each device object "ent.device.mdadmLine()". This is all good, but when other mdN devices that are not in the object list (for whatever reason, look at bug :), are needed to boot the system properly after update or install, this method might present a problem. I just say: "use mdadm". Patch attached.
Like I said on IRC yesterday, this sounds sane to me. So let's try it,
we'll see if anything breaks :-)
Jeremy
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
I guess if anybody runs into an install (with raid) that is not bootable, its probably, my fault. So feel free to scream at me :)
Regards
--
Joel Andres Granados
Red Hat / Brno, Czech Republic
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
