From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev and usb.agent
Date: Fri, 28 Oct 2005 01:09:51 +0000 [thread overview]
Message-ID: <20051028010951.GB31472@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0510151611080.8404@terminal.gregs.com>
On Thu, Oct 27, 2005 at 12:36:27PM +0200, Olivier Blin wrote:
> Greg Bell <gregbell@znet.com> writes:
>
> >> Catch up! udev does _all_ hotplug today.
> >
> > Oh, oops. OK I've done some more reading. However the FAQ at
> > http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ
> >
> > ...says/implies that udev is for creating the /dev nodes and not much else
> > because that's where devfs went wrong (trying to do too much). They even
> > refer the reader to HAL for the fancier more desktopy stuff.
>
> Maybe the udev FAQ should be updated then.
> It's quite confusing to read this:
> "udev is for managing /dev, not loading kernel drivers."
Done.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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:[~2005-10-28 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 6:14 udev and usb.agent Greg Bell
2005-10-15 18:27 ` Kay Sievers
2005-10-15 23:33 ` Greg Bell
2005-10-16 11:57 ` Kay Sievers
2005-10-17 0:42 ` Greg Bell
2005-10-17 1:44 ` Kay Sievers
2005-10-27 10:36 ` Olivier Blin
2005-10-28 1:09 ` Kay Sievers [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=20051028010951.GB31472@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).