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 23:58:42 +0000 [thread overview]
Message-ID: <20060104235842.GB16225@kroah.com> (raw)
In-Reply-To: <E1EuFWw-00065W-GO@mail.sourceforge.net>
On Wed, Jan 04, 2006 at 05:56:37PM -0500, Brian Sammon wrote:
> > 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?
>
> That's a good question. Debian says that recent 2.6 kernel packages "require"
> udev.
That's a Debian issue, 2.6 kernels do not require this.
> Based on that, and the fact that recent kernels have a udev line in
> the "Current Minimal Requirements" section of Documentation/Changes, I
> (wrongly, it seems) inferred that something had changed in recent
> (kernel.org) kernel sources that made them incompatible with hotplug.
No, not at all, that's there to show the version of udev that you need
to use, if you want to use it. Older versions will not work with that
specific kernel version.
> Since I often compile my own kernel, I suppose I don't have to obey
> debian kernel policies too closely.
Heh, if at all :)
> Considering my lack of interest in dynamic /dev filesystem support, which of
> hotplug
> hotplug-ng
> udev
> would people here recommend I use?
Just plain hotplug will probably work for you, if all you want is the
automatic module loading.
hotplug-ng is a dead project, it was replaced with a single udev rule
(that one previously mentioned), so don't use it.
> I notice that there hasn't been a new hotplug release in over a year. Is it
> unmaintained, or has it simply not needed updating?
Pretty much both. I have a bunch of patches floating around that the
last release needs, but as distros are moving away from it, I'm loath to
do a new release.
But maybe I need to flush out the pending stuff, and mark it
"depreciated"...
thanks,
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
prev parent reply other threads:[~2006-01-04 23:58 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
2006-01-04 22:56 ` Brian Sammon
2006-01-04 23:06 ` Aras Vaichas
2006-01-04 23:58 ` 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=20060104235842.GB16225@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).