From: Gene Heskett
Date: Thu Nov 11 2004 - 01:02:51 EST

On Wednesday 10 November 2004 19:19, Greg KH wrote:
>On Wed, Nov 10, 2004 at 07:06:37PM -0500, Gene Heskett wrote:
>> On Wednesday 10 November 2004 16:03, Alexandre Costa wrote:
>> >On Wed, 10 Nov 2004 15:46:06 -0500 (EST), linux-os
>> >
>> ><linux-os@xxxxxxxxxxxxxxxxxx> wrote:
>> >> What is the approved substitute for DEVFS_FS that is marked
>> >> obsolete?
>> >
>> >udev
>> >
>> Humm, I'm not sure I'm entirely happy with that choice. I have an
>> FC3RC5 install on an old P-II running at 233mhz, and the udev
>> start in the bootup is the slowest single thing to get started by
>> an order of magnitude.
>> Can someone tell me a good reason udev wastes as much time as the
>> post does checking 383 megs of memory, which is very nearly a
>> minute even just for udev?
>It's all up to the rules you are using for udev. If you have udev
> rules that call out to scripts for every device (like I think the
> SuSE default install does), udevstart can take a long time.
This is a box stock FC3RC5 install, Greg. I haven't touched a thing
in how it works because I don't know anything about it, other than
its about 1/3rd of the total boot time.

>If you don't have any external dependancies, udevstart is fast.
>> If its to be used, its got to speed itself up, a LOT!.
>Please post what version of udev you are using, and what your udev
> rules file looks like.

Probably see the FC3 release, but I don't know how much diff there is
between RC5 and the final, rsync is trying to convert mine to final
right now. Where is this rules file?

>greg k-h

Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.28% setiathome rank, not too shabby for a WV hillbilly attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at