|
Great - thanks for doing this Dave.
And spill the beans about disk partitions - the sooner we
hear about it, the sooner we can figure out how to get around it
;-)
Thanks,
Bernard
Running MAKEDEV is a
manual _expression_ of installing the RPM.
I’ll do some
investigations to see what the proper approach is; I’m fairly certain I
already know the answer, but want to confirm that I don’t propose a
transitional model that will not be supported.
BTW, only marginally
related, we’ll apparently have some issues to resolve w/ disk partitions on
RHEL4.
--
David N.
Lombard
My comments represent
my opinions, not those of Intel Corporation.
From: Bernard
Li [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005 9:46
AM
To: Lombard, David N;
[email protected]
Subject: RE: [Oscar-devel] Support for
Fedora Core 3 and Mandrake 10.1
Hi
Dave:
I actually installed
the dev RPM from Fedora Core 2 on a Fedora Core 3 image, and it
worked.
But as you mention,
it is not used any more so maybe we shouldn't take this route - do you have
any suggestions? Perhaps run MAKEDEV manually, then?
Cheers,
Bernard
From:
Lombard, David N [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005
7:45
To: Bernard Li;
[email protected]
Subject: RE: [Oscar-devel] Support for
Fedora Core 3 and Mandrake 10.1
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:
[email protected]
Subject: [Oscar-devel] Support for
Fedora Core 3 and Mandrake 10.1
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.
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'.
|
