From: David Dodge <dododge@smart.net>
To: Greg KH <greg@kroah.com>
Cc: "Guo, Min" <min.guo@intel.com>, Steven Dake <sdake@mvista.com>,
Lars Marowsky-Bree <lmb@suse.de>,
Mark Bellon <mbellon@mvista.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hotplug-devel@lists.sourceforge.net,
cgl_discussion@osdl.org, "Ling,
Xiaofeng" <xiaofeng.ling@intel.com>
Subject: Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Thu, 30 Oct 2003 19:45:08 -0500 [thread overview]
Message-ID: <200310310045.TAA04280@smarty.smart.net> (raw)
Greg KH writes:
> On Wed, Oct 29, 2003 at 01:12:26PM +0800, Guo, Min wrote:
> > 2.For non-hotplug device
[...]
> > uDEV:
> > not deal with it
>
> See Robert Love's very simple script to populate stuff from sysfs. It
> can run from initscript just like SDE. But in the end, udev will end up
> in initramfs and we will not need to do this.
So the intent is to have compiled-in drivers for already-attached
devices (framebuffer, system disks, loop, whatever) generate calls to
/sbin/hotplug within initramfs?
Mainly I'm asking because I did try putting a hotplug script into an
initramfs a few weeks ago (using -test7), and it didn't appear to be
invoked for e.g. the VESA framebuffer. So I want to make sure this is a
"future" capability and not something that should have worked :-)
next reply other threads:[~2003-10-31 0:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-31 0:45 David Dodge [this message]
2003-10-31 0:58 ` ANNOUNCE: User-space System Device Enumation (uSDE) Greg KH
2003-10-31 2:29 ` Dave Dodge
-- strict thread matches above, loose matches on Subject: below --
2003-10-29 5:12 Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-27 20:41 Mark Bellon
2003-10-27 21:00 ` Lars Marowsky-Bree
2003-10-27 21:14 ` Mark Bellon
2003-10-28 11:00 ` Lars Marowsky-Bree
2003-10-28 18:12 ` Steven Dake
2003-10-28 22:44 ` Greg KH
2003-10-27 23:15 ` Steven Dake
2003-10-27 23:19 ` Mark Bellon
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=200310310045.TAA04280@smarty.smart.net \
--to=dododge@smart.net \
--cc=cgl_discussion@osdl.org \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lmb@suse.de \
--cc=mbellon@mvista.com \
--cc=min.guo@intel.com \
--cc=sdake@mvista.com \
--cc=xiaofeng.ling@intel.com \
/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).