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: [adventure] replace /sbin/hotplug by udevd
Date: Fri, 19 Nov 2004 00:55:14 +0000	[thread overview]
Message-ID: <20041119005514.GA12153@kroah.com> (raw)
In-Reply-To: <20041118002726.GA4281@vrfy.org>

On Wed, Nov 17, 2004 at 09:04:55PM -0700, Kevin P. Fleming wrote:
> Kay Sievers wrote:
> 
> >This experimental patch changes udevd/udev to handle the _whole_ hotplug
> >event from the kernel up to the multiplexing of /etc/hotplug.d/. It
> >should solve most of the current shortcomings of the hotplug event 
> >handling:
> >  - sysfs if not fully populated at event time
> >  - at device disconnect/reconnect, the "remove" may beat the "add"
> >  - an event may already work on the same DEVPATH
> >  - the hotplug scripts don't know the device node name
> >  - the total count of event processes can't be controlled
> 
> This is very, very cool. What a major simplification of the whole 
> process, with the addition of interesting new features as well.
> 
> What is the likely timeframe for this to make it into udev proper?

The main "problem" with this is for people who don't want to run udev on
their machines.  They are happy with their static dev, yet they want to
have the hotplug package manage their modules, and do the other fun
stuff (like HAL).  If udev requires that it take over the hotplug
multiplexer, then anyone who doesn't use udev looses out from the good
things that HAL and anyone who relies on the functionality that this new
udevd provides can't ensure that all users will actually have it
running.

Did that make sense?

I don't know how to resolve this issue right now :(

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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:[~2004-11-19  0:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18  0:27 [adventure] replace /sbin/hotplug by udevd Kay Sievers
2004-11-18  1:25 ` Greg KH
2004-11-18  4:04 ` Kevin P. Fleming
2004-11-18  6:40 ` Stefan Schweizer
2004-11-18 23:47 ` Kay Sievers
2004-11-19  0:03 ` Kay Sievers
2004-11-19  0:55 ` Greg KH [this message]
2004-11-19  1:11 ` Kay Sievers
2004-11-19  7:27 ` Greg KH
2004-11-19 16:03 ` Kay Sievers

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=20041119005514.GA12153@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).