From: Marc G. <gr...@at...> - 2009-02-08 13:02:15
|
Hi Gordan, On Thursday 05 February 2009 23:11:24 Gordan Bobic wrote: > It would appear that OSR doesn't start up MD software RAID arrays. yes. > > Well, now it does. Patches attached. :) ;-) How and were are you using md? > > It fires up any MD arrays that can be assembled right after the DM > arrays. I'm not sure if this should be made optional (only do it if > mdadm is present, which will only be the case of the mdadm.list files > are added to the initrd. Any thoughts on this? Good question. I'm not sure. I would love to have it only if you want it. But how can an md-device be detected? > > On an unrelated note, mkinitrd seems to put all the .pyc and .pyo files > into the initrd. I only found this out because I wiped them while > troubleshooting the cdslDefaults_element issue, since it complains those > files are not there. Are these really necessary? I would have thought > those non-essential, and anything making the initrd smaller is probably > a good thing... Speaking of which, did my mkinitrd -l parameter optional > "diet" kernel module patch ever make it into the trunk? No, not yet. I didn't forget it but had no time to reallly think about it. I'm still not sure how to use it best. With the python packages. The .pyo/pyc is a point. I'll think about adding something like <package> *.py to the listfiles listing python rpms. That means only files with .py in the end will be included. And no I don't think it works negative. ;-) Regards Marc. > > Thanks. > > Gordan -- Gruss / Regards, Marc Grimme http://www.atix.de/ http://www.open-sharedroot.org/ |