linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug and udev - a question
Date: Sun, 02 Apr 2006 20:24:17 +0000	[thread overview]
Message-ID: <20060402202417.GA28614@kroah.com> (raw)
In-Reply-To: <ada605fb0603310036s68fdb8d0x3fc6d73d135ffd7e@mail.gmail.com>

On Sun, Apr 02, 2006 at 05:04:30PM +0300, John Que wrote:
> Hello,
> 
> Thanks for the link!
> I read it carefully; all of it , except of the last 2
> paragraphs, deal mainly with hotplug and improvements that
> were made in hotplug-ng.
> 
> Now, to the last 2 paragrapghs:
> 
> >With the release of the 050 release of udev, if /sbin/udevsend is the kernel
> >hotplug program (it can be changed by modifying the value of the
> >/proc/sys/kernel/hotplug file), then it operates like the original
> >/etc/hotplug.d multiplexer program as well as handling all of the udev device
> >node generation. This ensures that the /etc/hotplug.d/ invocations
> happen in the
> >proper order, and in sequence for the same device. Gentoo Linux
> already supports
> >this mode of operation.
> 
> >However, not every user wants to use udev. Because of that, the hotplug-ng
> >project is continuing, even if it seems like they are competing against each
> >other in implementing the same functionality. As the same developers are doing
> >the work in both programs, all users of Linux benefit with a faster module
> >loading process, and further advancements in hotplug functionality.
> 
> 
> What I don't get from here is what is exactly the advantage
> of using udev solely over using udev with hotplug and what
> is the exact reason that hotplug is deprecated.
> Is it because there is some functionality which is duplicated
> in udev and in hotplug ? or some other reason ?

Turns out you can do everything that hotplug did with just about 1 udev
rule.  So that makes the hotplug package obsolete.

Now the hotplug package did do a few other odd things (firmware loading,
etc.) that has been moved over to udev with external scripts for those
systems that only use udev instead of hotplug.  So if you do this,
please be aware of this.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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

  parent reply	other threads:[~2006-04-02 20:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-31  8:36 Hotplug and udev - a question John Que
2006-03-31 10:41 ` Chris Smith
2006-03-31 17:17 ` Greg KH
2006-04-02 14:04 ` John Que
2006-04-02 20:21 ` Chris Smith
2006-04-02 20:24 ` Greg KH [this message]
2006-04-10 14:03 ` Anssi Saari
2006-04-11 10:57 ` juuso.alasuutari

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=20060402202417.GA28614@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).