From: "Kevin P. Fleming" <kpfleming@starnetworks.us>
To: linux-hotplug@vger.kernel.org
Subject: Re: Minimal static dev entries?
Date: Sun, 15 May 2005 03:31:58 +0000 [thread overview]
Message-ID: <4286C2AE.1070005@starnetworks.us> (raw)
In-Reply-To: <4286C122.5050106@ipom.com>
Phil Dibowitz wrote:
> So my question is... is there anything else that _should_ be in the
> static dev filesystem that's needed until udev get's started? udev is
> started extraordinarily early in the boot process, so I don't suspect
> so, but I thought I'd ask those who know best.
No, in my experience the only entries needed are /dev/console and /dev/null.
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_ids93&alloc_id\x16281&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-05-15 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 3:25 Minimal static dev entries? Phil Dibowitz
2005-05-15 3:31 ` Kevin P. Fleming [this message]
2005-05-16 18:54 ` Greg KH
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=4286C2AE.1070005@starnetworks.us \
--to=kpfleming@starnetworks.us \
--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).