linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Dibowitz <phil@ipom.com>
To: linux-hotplug@vger.kernel.org
Subject: Minimal static dev entries?
Date: Sun, 15 May 2005 03:25:22 +0000	[thread overview]
Message-ID: <4286C122.5050106@ipom.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

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.

Thanks,
-- 
Phil Dibowitz                             phil@ipom.com
Freeware and Technical Pages              Insanity Palace of Metallica
http://www.phildev.net/                   http://www.ipom.com/

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
 - Benjamin Franklin, 1759


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

             reply	other threads:[~2005-05-15  3:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-15  3:25 Phil Dibowitz [this message]
2005-05-15  3:31 ` Minimal static dev entries? Kevin P. Fleming
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=4286C122.5050106@ipom.com \
    --to=phil@ipom.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).