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: udev for /dev
Date: Fri, 20 Feb 2004 19:25:48 +0000	[thread overview]
Message-ID: <200402201425.54197.vapier@gentoo.org> (raw)
In-Reply-To: <20040220062015.85721.qmail@web14907.mail.yahoo.com>

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

On Friday 20 February 2004 11:58 am, Frédéric L. W. Meunier wrote:
> On Thu, 19 Feb 2004, Jon Smirl wrote:
> > First question, isn't there a script for rebuilding the /dev directory?
>
> If it's to rebuild the static /dev that came with your
> distribution, reinstall the appropriate package. Probably
> dev-*.

or just run `MAKEDEV generic-i386` in /dev/

> > Second issue, I was forced to put a single device,
> > /dev/console into /dev to make this work. I discovered this
> > because I had deleted all of the common nodes out of /dev.
> > Apparently it needs to be there in the transition from initrd
> > to the boot device. Can this be avoided? This is a real mess
> > if you delete /dev/console. I spent a couple of hours with my
> > rescue disk before I figured out what happened.
>
> The same here. init needs it.

no, no one *needs* it ... i think i posted an e-mail here about it before but 
it's only 'needed' if you want to see output before the *getty apps are 
started.  the kernel will open that device node before executing init so that 
init will have the proper stdout file descriptor to write to.  if you dont 
have /dev/console, the kernel prints the warning about not being able to open 
it, and then just runs init which works *fine* without the node.
-mike

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

  parent reply	other threads:[~2004-02-20 19:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20  6:20 udev for /dev Jon Smirl
2004-02-20  6:26 ` Jon Smirl
2004-02-20 16:19 ` Jon Smirl
2004-02-20 16:36 ` John L Fjellstad
2004-02-20 16:50 ` Frédéric L. W. Meunier
2004-02-20 16:58 ` Frédéric L. W. Meunier
2004-02-20 17:13 ` Marco d'Itri
2004-02-20 17:38 ` Jon Smirl
2004-02-20 17:39 ` Marco d'Itri
2004-02-20 17:49 ` Jon Smirl
2004-02-20 19:25 ` Mike Frysinger [this message]
2004-02-20 21:41 ` Jon Smirl
2004-02-20 22:06 ` Jon Smirl
2004-02-23  7:37 ` mjl
2004-02-26  6:10 ` Jon Smirl
2004-02-28  0:32 ` 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=200402201425.54197.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).