From: Greg KH <gregkh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] contents of /dev after initial installation
Date: Thu, 1 Dec 2005 20:43:32 -0800 [thread overview]
Message-ID: <20051202044331.GA5732@kroah.com> (raw)
In-Reply-To: <20051202034459.GB2550@ols-dell.iic.hokudai.ac.jp>
On Fri, Dec 02, 2005 at 12:45:00PM +0900, Georgi Georgiev wrote:
> maillog: 02/12/2005-02:47:55(+0000): Stephen Bennett types
> > On Fri, 02 Dec 2005 03:35:23 +0100
> > Matthias Langer <mlangc@gmx.at> wrote:
> >
> > > revealed that there are in fact hundrets of premade device nodes in
> > > the /dev directory. And this is not only true for the box where i
> > > discovered this, which was brought up from a 2004.x cd, but also true
> > > for the box where i just installed gentoo from 2005.1-r1.
> > >
> > > Is there any reason for this ?
> >
> > Not all systems use udev or devfs. Plus, it's nice to be able to boot
> > the system when your dynamic /dev management fails for whatever reason.
>
> I don't need a fully populated /dev to get a working shell with
> init=/bin/bash on the kernel cmdline. And at that point it is easy to
> run /dev/MAKEDEV and get whatever devices are needed for
> troubleshooting.
>
> I of course assume that if the dynamic /dev management fails, then we
> need to *recover* instead of trying to get the system up as usual. And I
> also assume that the init scripts will anyway tell me "fatal error: give
> root password for maintenance or Ctrl-D to continue" if I have something
> vital missing from /dev.
If udev fails, and you have a completly empty /dev, you will not get any
console output at all for this type of message to be shown :(
So it's better to be safe than sorry.
That being said, my boxes have an empty /dev...
thanks,
greg k-h
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-02 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 2:35 [gentoo-dev] contents of /dev after initial installation Matthias Langer
2005-12-02 2:47 ` Stephen Bennett
2005-12-02 3:45 ` Georgi Georgiev
2005-12-02 3:57 ` Stephen Bennett
2005-12-02 5:32 ` Georgi Georgiev
2005-12-02 4:43 ` Greg KH [this message]
2005-12-02 13:17 ` Mike Frysinger
2005-12-02 17:00 ` Greg KH
2005-12-02 18:08 ` Mike Frysinger
2005-12-02 20:18 ` Matthijs van der Vleuten
2005-12-02 20:40 ` Mike Frysinger
2005-12-02 13:16 ` Mike Frysinger
2005-12-02 14:15 ` Petteri Räty
2005-12-02 14:46 ` Mike Frysinger
2005-12-24 15:43 ` Bjarke Istrup Pedersen
2005-12-24 18:59 ` Mike Frysinger
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=20051202044331.GA5732@kroah.com \
--to=gregkh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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