From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 003 release
Date: Tue, 21 Oct 2003 20:56:53 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106682570202661@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106637061520169@msgid-missing>
On Tue, Oct 21, 2003 at 10:20:47PM +0200, Martin Schlemmer wrote:
> > > Also, I am using ramfs for now to do the device nodes, and have not
> > > looked at minimal /dev layout, although I guess it is not that minimal,
> > > as even the input drivers lack udev (sysfs) support currently it seems.
> > > Wat was the last eta for initramfs again ?
> >
> > initramfs is in the kernel, you use it to boot already :)
> >
>
> OK ... I do though remember you saying it should be possible to have
> initramfs get the initial /dev going ... any docs on that ?
Other than the source in the kernel, no, sorry.
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
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
prev parent reply other threads:[~2003-10-21 20:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 5:56 [ANNOUNCE] udev 003 release Greg KH
2003-10-17 6:32 ` Clemens Schwaighofer
2003-10-17 17:57 ` clemens
2003-10-17 18:19 ` Greg KH
2003-10-17 18:27 ` Greg KH
2003-10-18 14:56 ` Kay Sievers
2003-10-19 21:01 ` Greg KH
2003-10-20 2:53 ` Kay Sievers
2003-10-20 10:14 ` Kay Sievers
2003-10-20 22:35 ` Greg KH
2003-10-21 0:50 ` Greg KH
2003-10-21 2:43 ` Greg KH
2003-10-21 17:44 ` Greg KH
2003-10-21 20:56 ` Greg KH [this message]
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=marc-linux-hotplug-106682570202661@msgid-missing \
--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).