From: Stephen Bennett <spb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] contents of /dev after initial installation
Date: Fri, 2 Dec 2005 03:57:20 +0000 [thread overview]
Message-ID: <20051202035720.0be09805@localhost> (raw)
In-Reply-To: <20051202034459.GB2550@ols-dell.iic.hokudai.ac.jp>
On Fri, 2 Dec 2005 12:45:00 +0900
Georgi Georgiev <chutz@gg3.net> wrote:
> 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.
Still more effort than booting into a system that is pretty much
fully-functional already to fix it.
> 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.
See above. And that still doesn't address the issue that some people
don't even want dynamic device management in the first place.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-02 3:57 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 [this message]
2005-12-02 5:32 ` Georgi Georgiev
2005-12-02 4:43 ` Greg KH
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=20051202035720.0be09805@localhost \
--to=spb@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