From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Do I want to use udev?
Date: Wed, 04 Jan 2006 21:21:39 +0000 [thread overview]
Message-ID: <20060104212139.GA12225@kroah.com> (raw)
In-Reply-To: <E1EuFWw-00065W-GO@mail.sourceforge.net>
On Wed, Jan 04, 2006 at 03:47:06PM -0500, Brian Sammon wrote:
> I'm trying to figure out if I should be using udev, and if so, how.
> I'm upgrading to a recent 2.6 kernel, and various documentation says that udev
> is required, but I'm not sure.
>
> I'm not interested in having a dynamic /dev filesystem (for the moment); a
> static /dev filesystem has served me just fine up to this point, and I think
> it will continue to work for a little while longer.
>
> So that leaves me with the other hotplug-related functionality, automatic
> driver loading. I can't figure out if, or how, udev does that.
The single rule:
ENV{MODALIAS}="?*", RUN+="/sbin/modprobe $env{MODALIAS}"
will cause udev do that.
> In particular, 99% of the hotplugging I do is USB devices, and I can't
> find any file in my (Debian) udev package that configures which USB
> drivers get loaded for which USB devices.
That's the "magic" of the kernel driver providing a
MODULE_DEVICE_TABLE() logic with the modprobe program matching up module
aliases. See my very old OLS 2001 paper on the basic ideas behind the
whole thing (but it's simpler now, as modprobe does the matching for us,
we don't have to scan the alias tables anymore by hand.)
> This leads me to wonder-- can I disable/uninstall udev altogether, or just
> disable the dynamic /dev filesystem and still have automatic USB driver
> loading?
You can, if you only use the one rule above :)
But if that's all that you want to have happen, stick with the old
hotplug package, it still works just fine. Why would you want to use
udev if you don't care about persistant names and other good stuff it
provides?
> If part/all of my problem is debian specific, I'd still appreciate general
> information, such as how it should be done, or information about how this
> works on your system.
I suggest you ask debian udev specific questions on a debian specific
mailing list, you might have better luck that way :)
Hope this helps,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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
next prev parent reply other threads:[~2006-01-04 21:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 20:47 Do I want to use udev? Brian Sammon
2006-01-04 21:21 ` Greg KH [this message]
2006-01-04 22:56 ` Brian Sammon
2006-01-04 23:06 ` Aras Vaichas
2006-01-04 23:58 ` Greg KH
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=20060104212139.GA12225@kroah.com \
--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).