From: Grant Edwards <grante@visi.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: No /dev entries in recent stage3 snapshots?
Date: Wed, 21 Jan 2009 15:33:23 +0000 (UTC) [thread overview]
Message-ID: <gl7f82$fm5$1@ger.gmane.org> (raw)
In-Reply-To: 1232524334.9583.13.camel@mymachine
On 2009-01-21, Dirk Heinrichs <dirk.heinrichs.ext@nsn.com> wrote:
> Am Mittwoch, den 21.01.2009, 04:04 +0000 schrieb ext Grant Edwards:
>
>> I'm a little confused. Is there supposed to be an additional
>> installation step to populate the /dev directory when using
>> recent stage3 snapshots?
>
> One usually bind-mounts /dev, /proc and /sys into the chroot, like
>
> mount --bind /dev /newinstall/dev # dito for /proc, /sys
> chroot /newinstall
> If this isn't documented, you should file a bug.
That's docuemented in the "normal" install doc, but not in the
quick install doc.
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.
--
Grant Edwards grante Yow! RELATIVES!!
at
visi.com
next prev parent reply other threads:[~2009-01-21 15:33 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 ` Grant Edwards [this message]
2009-01-21 15:50 ` [gentoo-user] " 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
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='gl7f82$fm5$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