> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:cooker-owner@linux-
> mandrake.com] On Behalf Of Chmouel Boudjnah
> Sent: Sunday, August 05, 2001 6:01 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Cooker] kernel-2.4.7-6mdk
>
> Tony Clark <[EMAIL PROTECTED]> writes:
>
> > I am just thinking about installing this kernel. I havbe been
noticing
> a bit
> > of talk that the latest kernels are built for devfs by default. Is
this
> > correct? I don't really want to fiddle with devfs right now. from
> memory
> > you can disable devfs by passing something to lilo at boot time?
>
> you can rpm --nodeps devfsd for that.
It's not as simple. By default devfs is not mounted, it means you have
your old /dev with old contents. Devfsd is not started as well, so the
above really is not needed, you can install devfsd and it does no harm.
But some things change *even* if devfs is not mounted. The most notable
case being /proc/partitions, but I guess it is already fixed for
bootloaders (installkernel). But, of course, any package that is trying
to access /proc/partitions must be prepared to deal with it.
To another questions in this thread - AFAIK defvs is pretty stable and
IMHO is good idea. If some driver does not support it, the correct thing
is to fix driver.
Of course, devfs was designed wit really large configurations in mind.
For small desktop system you probably do not need it.
-andrej
