linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kasper Sandberg <postmaster@metanurb.dk>
To: linux-hotplug@vger.kernel.org
Subject: Re: linux hotplug/hotplug-ng
Date: Sun, 14 Aug 2005 14:12:10 +0000	[thread overview]
Message-ID: <1124028730.31459.4.camel@localhost> (raw)
In-Reply-To: <1123747167.31868.11.camel@localhost>

On Thu, 2005-08-11 at 11:20 -0700, Greg KH wrote:
<snip>
> 
> Yes, as I said above, hotplug-ng is obsolete, you can do everything it
> did with just one udev rule :)
> 
> Anyway, here's how things are shaking themselves out:
> 
> udev will replace hotplug and hotplug-ng entirely.  It almost does this
> already today in the Gentoo tree, but I need to spend a bit more time to
> tweak things properly to get it completly there.  To do that we will
> just rely on the hotplug netlink messages coming out of the kernel and
> set /proc/sys/kernel/hotplug to NULL.  udev will handle all of these
> messages, and shuttle them off to their proper places if needed.
> Combine udev with HAL and you pretty much have the full functionality of
> the old hotplug package, with lots of extra goodies added (speed,
> persistant naming, desktop notification, etc.)
> 
> An example of a distro that does all of this today is SuSE 10, you can
> take a look at it in the opensuse download.  Kay is the one who got this
> all working properly, not me.
> 
> Does this help out any?  
> 
yes, allthough i dont understand fully how udev can do this, except if
it catches the hotplug messages from the kernel..

your idea seems very good, and i would like to help.. if you are
interrested in me helping, you are welcome to msg me on irc(redeeman) or
mail me..

> So, thanks for the hotplug-ng ebuild, but it's not going to be necessary
> anymore.
> 
> thanks,
> 
> greg k-h
> 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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:[~2005-08-14 14:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  7:59 linux hotplug/hotplug-ng Kasper Sandberg
2005-08-11 13:48 ` Alexander E. Patrakov
2005-08-11 18:20 ` Greg KH
2005-08-12  0:09 ` Kasper Sandberg
2005-08-14 14:12 ` Kasper Sandberg [this message]
2005-08-14 19:33 ` Kay Sievers
2005-08-15  4:01 ` Kasper Sandberg

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=1124028730.31459.4.camel@localhost \
    --to=postmaster@metanurb.dk \
    --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).