All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Smith <smitty_one_each@bigfoot.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug and udev - a question
Date: Sun, 02 Apr 2006 20:21:24 +0000	[thread overview]
Message-ID: <87bqvjybi3.fsf@bigfoot.com> (raw)
In-Reply-To: <ada605fb0603310036s68fdb8d0x3fc6d73d135ffd7e@mail.gmail.com>

>>>>> "John" = John Que <qwejohn@gmail.com> writes:
    John> What I don't get from here is what is exactly the advantage
    John> of using udev solely over using udev with hotplug and what
    John> is the exact reason that hotplug is deprecated.  Is it
    John> because there is some functionality which is duplicated in
    John> udev and in hotplug ? or some other reason ?

Take this with a grain of salt, but my understanding is that, from a
kernel perspective, the udev way is smaller, simpler, and more
flexible.
Best,
Chris



-------------------------------------------------------
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:21 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 [this message]
2006-04-02 20:24 ` Greg KH
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=87bqvjybi3.fsf@bigfoot.com \
    --to=smitty_one_each@bigfoot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.