public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: No /dev entries in recent stage3 snapshots?
Date: Fri, 23 Jan 2009 04:49:48 +0000 (UTC)	[thread overview]
Message-ID: <glbi9b$lmm$1@ger.gmane.org> (raw)
In-Reply-To: 20090121155655.466edba0@zaphod.digimed.co.uk

On 2009-01-21, Neil Bothwick <neil@digimed.co.uk> wrote:
> On Wed, 21 Jan 2009 15:50:17 +0000, Nick Cunningham wrote:
>
>>> But, that doesn't really solve the problem, since after a
>>> reboot the /dev directory will be empty again and you end up
>>> with problems such as no console during startup.
>
>> IIRC thats because /dev should be populated on startup by udev
>> so i would check that udev is installed and working properly,
>> if you use openrc then this could be the cause as openrc now
>> starts udev through normal scripts i think, sometimes on
>> upgrade from baselayout 1 they may not be automatically added
>> to the right runlevels.
>
> You still need /dev/console in the dev directory of the root partition,
> along with /dev/null.

Try telling that to somebody in the Gentoo forum hiding behind
the screen name "desultory".  Sheesh.  I reported the issue to
the forum thread as requested by the article on www.gentoo.org,
and I got a very hostile reaction.  Bascially I got a snide,
insulting response, a complete denial that there was a problem
with the tarball in question, and a denial that either
/dev/console or /dev/null is needed at boot time.

That's the last time I waste my time with that forum.  I should
have known. Web forums all suck.  Web forum UIs are all
completely abominable, and they seem to be inhabited almost
exclusively by surly, unjustifiably arrogant junior-high kids
hiding behind stupid screen names and even worse avatars.

> Anything else is a waste of disk space and inodes as the
> static /dev/devices are hidden as soon as udev starts.

Yup.

> If the tarball doesn't contain /dev/console it is broken, but
> it is also broken if it contains thousands of device entries. 

-- 
Grant





  parent reply	other threads:[~2009-01-23  4:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  4:04 [gentoo-user] No /dev entries in recent stage3 snapshots? Grant Edwards
2009-01-21  5:42 ` [gentoo-user] " Grant Edwards
2009-01-21  7:52 ` [gentoo-user] " Dirk Heinrichs
2009-01-21  8:31   ` Nickolas Fortino
2009-01-21 15:33   ` [gentoo-user] " Grant Edwards
2009-01-21 15:50     ` Nick Cunningham
2009-01-21 15:56       ` Neil Bothwick
2009-01-21 16:48         ` Grant Edwards
2009-01-21 17:38           ` Dirk Heinrichs
2009-01-21 18:31             ` Grant Edwards
2009-01-23  4:49         ` Grant Edwards [this message]
2009-01-23  4:55           ` Volker Armin Hemmann
2009-01-23  5:17             ` Grant Edwards
2009-01-23  5:39               ` Volker Armin Hemmann
2009-01-23 14:48                 ` Grant Edwards
2009-01-25  7:12                   ` Dirk Heinrichs
2009-01-24 23:29             ` Neil Bothwick
2009-01-25  1:29               ` Grant Edwards
2009-01-25  1:37                 ` Grant Edwards
2009-01-25  6:19                   ` Dale

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='glbi9b$lmm$1@ger.gmane.org' \
    --to=grante@visi.com \
    --cc=gentoo-user@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