linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: starting with an empty /dev
Date: Fri, 13 Feb 2004 17:58:25 +0000	[thread overview]
Message-ID: <200402131258.26552.vapier@gentoo.org> (raw)
In-Reply-To: <20040213102434.GA3991@wonderland.linux.it>

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

On Friday 13 February 2004 05:24 am, Marco d'Itri wrote:
> IIRC initramfs already contains these devices, but anyway it's important
> to remember that if they are removed everything will break.
> Should we start thinking about how udev could be used in the real world?

the devices that are needed are somewhat distro (well, init scripts) 
dependent ...

> Maybe you dont care but I have installed udev and it is working for me
> great. But there were some problems.

using /udev never even occurred to me ... i've been using udev on my /dev 
since 002 :x

> I have found that devices:
> /dev/null,
> /dev/console

like i said above, this is specific to your init scripts ...
/dev/console is needed if you want to see output from your init scripts ... 
you can boot *just fine* without it ... just wait a while into the getty's 
pop up :)
/dev/null is needed by your _init scripts_ ... many boot up scripts just pump 
their output into /dev/null and then when there are errors, they output happy 
little errors for the user to understand ... if, before you've loaded up 
udev, you try to pump into /dev/null and your / is ro, the init scripts are 
going to think the command it just tried to run failed and so in general, 
everything dies

i've already created a small patch for inclusion with the Gentoo baselayout to 
handle the case when /dev/null doesnt exist (yeah, i like to `rm -rf /dev/* ; 
sync ; reboot -nf` for fun ... no seriously, i do) that way if you dont have 
anything in /dev/, your machine will boot up and you can login to create 
whatever nodes you may need in order to have a 'normal' bootup (which is kind 
of where you're at matt, /dev/console and /dev/null)
-mike

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

      reply	other threads:[~2004-02-13 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-13 10:24 starting with an empty /dev Marco d'Itri
2004-02-13 17:58 ` Mike Frysinger [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=200402131258.26552.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --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).