public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: iSteve <isteve@rulez.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: udevstart surprisingly slow
Date: Mon, 30 Jan 2006 23:42:04 -0800	[thread overview]
Message-ID: <20060131074204.GA26356@kroah.com> (raw)
In-Reply-To: <43DE8D5E.2040905@rulez.cz>

On Mon, Jan 30, 2006 at 11:04:14PM +0100, iSteve wrote:
> Greetings,
> I've recently upgraded udev from 063 to 082 and then 084.
> 
> With 063, startup of udev was near-instant; with both 082 and 084, it 
> takes a significant ammount of time (~15s) to create the base devices 
> using udevstart or udevsynthesize (this one is taken from Debian, which 
> apparently in turn taken it from SuSE; the rest of codebase is vanilla).

With the 2.6.15 kernel, udevstart is no longer needed.  Please use the
recommended shell script instead (as posted to the linux-hotplug-devel
mailing list.)

> This issue appears on kernel 2.6.15.1 with SquashFS 2.2r2, SWSUP2 2.2 
> and VesaFB-TNG 1.0-rc1-r3 patches.

All of which are not patches included in the mainline kernel.  Can you
try it without these?

> The init script used simply mounts 10MiB tmpfs onto /dev, creates 
> /dev/.udev/{db,queue} directories, then runs udevd --daemon and then 
> udevsynthesize or udevstart (tried both, same result).

Again, don't do that :)

Also, udev specific questions like these are best asked on the
linux-hotplug-devel mailing list, as the udev documentation states.

thanks,

greg k-h

      reply	other threads:[~2006-01-31  7:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-30 22:04 udevstart surprisingly slow iSteve
2006-01-31  7:42 ` Greg KH [this message]

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=20060131074204.GA26356@kroah.com \
    --to=greg@kroah.com \
    --cc=isteve@rulez.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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