public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org, Alexandre Costa <alebyte@gmail.com>,
	linux-os@analogic.com
Subject: Re: DEVFS_FS
Date: Wed, 10 Nov 2004 16:19:11 -0800	[thread overview]
Message-ID: <20041111001909.GA18269@kroah.com> (raw)
In-Reply-To: <200411101906.37328.gene.heskett@verizon.net>

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@chaos.analogic.com> wrote:
> >> What is the approved substitute for DEVFS_FS that is marked
> >> obsolete?
> >
> >udev
> >http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev.html
> 
> 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.

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.

thanks,

greg k-h

  reply	other threads:[~2004-11-11  0:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 20:46 DEVFS_FS linux-os
2004-11-10 21:03 ` DEVFS_FS Alexandre Costa
2004-11-11  0:06   ` DEVFS_FS Gene Heskett
2004-11-11  0:19     ` Greg KH [this message]
2004-11-11  6:01       ` DEVFS_FS Gene Heskett
  -- strict thread matches above, loose matches on Subject: below --
2004-11-11 19:53 DEVFS_FS Adam J. Richter
2004-11-11 20:24 DEVFS_FS Adam J. Richter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041111001909.GA18269@kroah.com \
    --to=greg@kroah.com \
    --cc=alebyte@gmail.com \
    --cc=gene.heskett@verizon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox