From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Minimal static dev entries?
Date: Mon, 16 May 2005 18:54:38 +0000 [thread overview]
Message-ID: <20050516185438.GB10322@kroah.com> (raw)
In-Reply-To: <4286C122.5050106@ipom.com>
On Sat, May 14, 2005 at 08:25:22PM -0700, Phil Dibowitz wrote:
> As I moved my data from one disk to another (well actually from a disk
> to an md device) I used cp -ax which stays ona given filesystem, and
> thus I never get static /dev entries on my new root device.
>
> The only things that seem to be needed by the static boot prior to udev
> being started (i.e the only things to cause error) were /dev/console and
> /dev/null. So I made these two and the system now boots fine and udev
> gets started and in /dev/.static/dev I have console, null, and a named
> pipe called initctl.
>
> 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.
It all depends on your distro and its startup logic. Some don't need
any static nodes :)
thanks,
greg k-h
-------------------------------------------------------
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_idt12&alloc_id\x16344&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
prev parent reply other threads:[~2005-05-16 18:54 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
2005-05-16 18:54 ` 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=20050516185438.GB10322@kroah.com \
--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 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.