From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 010 release
Date: Tue, 23 Dec 2003 01:23:10 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-107214265220554@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-107214128619578@msgid-missing>
On Mon, Dec 22, 2003 at 04:58:09PM -0800, Greg KH wrote:
> I've released the 010 version of udev. It can be found at:
> kernel.org/pub/linux/utils/kernel/hotplug/udev-010.tar.gz
Oh, forgot to mention that udev runs a _lot_ slower now, taking at least
1 second for every device addition. This makes the initscript or the
test scripts take a long time.
This was done to try to fix the race condition where udev beats the
kernel before it has created all of the sysfs links and files. I need
some libsysfs changes before this can be done properly, without the big
speed hit (the libsysfs people are working on it.)
If anyone's interested in it, take a look at the FIXMEs in namedev.c.
I tried messing around with just a simple stat() call, but still
couldn't reliably get stuff to work for partitions on usb-storage
devices (which are slow to enumerate.) Any help here would be
apprecated.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2003-12-23 1:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:58 [ANNOUNCE] udev 010 release Greg KH
2003-12-23 1:23 ` 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=marc-linux-hotplug-107214265220554@msgid-missing \
--to=greg@kroah.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).