All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Kevin P. Fleming" <kpfleming@cox.net>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
	linux-kernel@vger.kernel.org,
	linux-hotplug-devel@lists.sourceforge.net
Subject: Re: small devfs patch for 2.5.65, plan to replace /sbin/hotplug
Date: Fri, 21 Mar 2003 15:21:31 -0800	[thread overview]
Message-ID: <20030321232131.GA18010@kroah.com> (raw)
In-Reply-To: <3E7B79D5.3060903@cox.net>

On Fri, Mar 21, 2003 at 01:45:09PM -0700, Kevin P. Fleming wrote:
> Adam J. Richter wrote:
> >	I believe that the only change in this version of devfs is
> >moving the code to invoke the user level devfs_helper program to a
> >separate file, fs/devfs/notify.c.  This change will simplify a future
> >code shrink inspired by David Brownell's suggesting that I think about
> >unifying hotplug with devfs.  In the future I would like to lift
> >fs/devfs/notify.c out of devfs so that the code that currently invokes
> >user level helpers for hot plug events can be replaced with two calls
> >to a renamed devfs_event() on
> >/sys/bus/<bustype>/devices/<bus#>/<whatever>, one for insertion and
> >one for removal.

Adam, right now we get /sbin/hotplug events for every device insertion
and removal in the kernel.  Do you want more than this?

> Are you still considering smalldevfs for 2.6 inclusion? If not, then I'd 
> like to discuss with you (and Greg KH) the possibility of just eliminating 
> devfs entirely, and moving to a userspace version that is driven entirely 
> by /sbin/hotplug.

You mean with something like this:
	http://www.linuxsymposium.org/2003/view_abstract.php?talk=94
:)

thanks,

greg k-h

  reply	other threads:[~2003-03-21 23:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21  9:40 small devfs patch for 2.5.65, plan to replace /sbin/hotplug Adam J. Richter
2003-03-21 19:16 ` Christoph Hellwig
2003-03-21 20:45 ` Kevin P. Fleming
2003-03-21 23:21   ` Greg KH [this message]
2003-03-21 23:41     ` Kevin P. Fleming
2003-03-21 23:54       ` Andrew Walrond
2003-03-22  0:03         ` Greg KH
2003-03-21 23:55       ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2003-03-21  9:40 Adam J. Richter
2003-03-21 19:16 ` Christoph Hellwig
2003-03-21 20:45 ` Kevin P. Fleming
2003-03-21 23:21 ` Greg KH
2003-03-21 23:41 ` Kevin P. Fleming
2003-03-21 23:54 ` Andrew Walrond
2003-03-21 23:55 ` Greg KH
2003-03-22  0:03 ` Greg KH
2003-03-22  3:39 ` Adam J. Richter
2003-03-22 15:36 ` jordan.breeding
2003-03-21 21:10 Adam J. Richter
2003-03-21 21:17 ` Christoph Hellwig
2003-03-21 21:30 Adam J. Richter
2003-03-22  3:39 Adam J. Richter
2003-03-22 15:36 jordan.breeding
2003-03-22 22:43 ` Nicholas Wourms

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=20030321232131.GA18010@kroah.com \
    --to=greg@kroah.com \
    --cc=adam@yggdrasil.com \
    --cc=kpfleming@cox.net \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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.