From: Andrew Walrond <andrew@walrond.org>
To: "Kevin P. Fleming" <kpfleming@cox.net>
Cc: Greg KH <greg@kroah.com>, "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 23:54:00 +0000 [thread overview]
Message-ID: <3E7BA618.3060603@walrond.org> (raw)
In-Reply-To: 3E7BA329.2060806@cox.net
Sounds wonderful. Any downsides?
Andrew Walrond
Kevin P. Fleming wrote:
> Greg KH wrote:
>
>>> 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
>> :)
>>
>
> Yep, that's the one. Sounds very simple and straightforward to me. The
> most complex part will be defining some file structure to define the
> user's desired naming policy to the agent that handles the hotplug events.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-03-21 23:44 UTC|newest]
Thread overview: 14+ 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
2003-03-21 23:41 ` Kevin P. Fleming
2003-03-21 23:54 ` Andrew Walrond [this message]
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 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=3E7BA618.3060603@walrond.org \
--to=andrew@walrond.org \
--cc=adam@yggdrasil.com \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox