From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] contents of /dev after initial installation
Date: Fri, 2 Dec 2005 18:08:21 +0000 [thread overview]
Message-ID: <20051202180821.GJ9185@toucan.gentoo.org> (raw)
In-Reply-To: <20051202170025.GA24674@kroah.com>
On Fri, Dec 02, 2005 at 09:00:25AM -0800, Greg KH wrote:
> On Fri, Dec 02, 2005 at 01:17:38PM +0000, Mike Frysinger wrote:
> > On Thu, Dec 01, 2005 at 08:43:32PM -0800, Greg KH wrote:
> > > That being said, my boxes have an empty /dev...
> >
> > you so sure about that ? if your /dev is completely empty, you wont
> > get any init output because the kernel cant find /dev/console ... and
> > the init scripts will get pissed when they try to pipe output into
> > /dev/null (before udev is started) and the command errors out with
> > /dev being read-only
>
> No, all of the /dev/null reliance has been fixed.
sure, in Gentoo it's been fixed (i know cause i fixed it), but every
other distro i know of the boot system would bomb
my e-mail was just a follow up because a lot of people think they can
safely nuke /dev and then dont understand why their machines dont boot
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-02 18:12 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
2005-12-02 13:17 ` Mike Frysinger
2005-12-02 17:00 ` Greg KH
2005-12-02 18:08 ` Mike Frysinger [this message]
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=20051202180821.GJ9185@toucan.gentoo.org \
--to=vapier@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