RE: [Oscar-devel] Support for Fedora Core 3 and Mandrake 10.1

[Lombard, David N]

Wait a second.  The old “dev” model, where an RPM created countless “devices” in /dev to accommodate every possible device a user may have is NOT used anymore.  Creating this RPM is wrong and (practically) guaranteed to fail.   -- David N. Lombard   My comments represent my opinions, not those of Intel Corporation. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bernard Li Sent: Tuesday, March 01, 2005 8:29 PM To: oscar-devel@lists.sourceforge.net Subject: [Oscar-devel] Support for Fedora Core 3 and Mandrake 10.1   Hey guys:   I have previously mentioned that support for Fedora Core 3 and Mandrake 10.1 cannot happen until systemconfigurator works with udev.  Turns out, udev was not the problem, it was the absence of dev (at least that's what I think is the case now).   I was prompted by Sean Dague (original author of systemconfigurator) to use lilo instead of grub when I build the image, and by doing so, it lead me to a discovery -   The /dev directory on the image is empty (except for 2 files) and this caused problems when systemconfigurator tries to set up the boot loader.   In Fedora Core 3 (and I assume Mandrake 10.1), they have removed the dev RPM.  This RPM basically creates the links to the commonly used devices in /dev.  We can get around this problem in 2 ways:   1) manually install the dev RPM on the image (since the distro CDs do not provide it, we have to ship it ourselves) 2) run the MAKEDEV program manually to create the links for the particular HD types that the user has for the nodes   This step needs to be done after the image is built, and before the image is deployed.   Comments?  Thoughts?   We can potentially fasttrack the support for Fedora Core 3 and Mandrake 10.1, pending some other issues - eg. will this work for grub also...?  And finding a modprobe.conf 'solution'.   Cheers,   Bernard