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]  No /dev entries in recent stage3 snapshots?
Date: Wed, 21 Jan 2009 04:04:43 +0000 (UTC)	[thread overview]
Message-ID: <gl66sr$pud$1@ger.gmane.org> (raw)

I'm doing an install using the quick-install doc and this weeks
stage3 snapshot, and I find I can't use scp or ssh once I've
chroot'ed.  Is that normal?

  livecd linux # scp 192.168.2.4:/usr/src/linux/.config .
  PRNG is not seeded

I noticed the same thing in the install I did a few days ago.
Later in that install grub failed to install and after
rebooting, my /dev directory was missing just about everything.

Here's the /dev directory in the chroot'ed environment I got
using stage3-i686-20090114.tar.bz2:

  livecd linux # ls -l /dev 
  total 12
  lrwxrwxrwx 1 root root   15 Jan 20 21:30 MAKEDEV -> ../sbin/MAKEDEV
  -rw-r--r-- 1 root root   75 Jan 20 21:49 null
  drwxr-xr-x 2 root root 4096 Jan 13 19:29 pts
  drwxr-xr-x 2 root root 4096 Jan 13 19:29 shm

I checked the contents of stage3-i686-20090114.tar.bz2, and
this is all that's there:

   $ tar tvf stage3-i686-20090114.tar.bz2 | fgrep ./dev
   drwxr-xr-x root/root         0 2009-01-13 21:20 ./dev/
   -rw-r--r-- root/root         0 2009-01-13 21:20 ./dev/null
   lrwxrwxrwx root/root         0 2009-01-13 19:29 ./dev/MAKEDEV -> ../sbin/MAKEDEV
   -rw-r--r-- root/root         0 2009-01-13 19:29 ./dev/.keep
   drwxr-xr-x root/root         0 2009-01-13 19:29 ./dev/shm/
   -rw-r--r-- root/root         0 2009-01-13 19:29 ./dev/shm/.keep
   drwxr-xr-x root/root         0 2009-01-13 19:29 ./dev/pts/
   -rw-r--r-- root/root         0 2009-01-13 19:29 ./dev/pts/.keep

In contrast, stage3-i686-2008.0.tar.bz2 has a fully populated
/dev/ tree:

   $ tar tvf stage3-i686-2008.0.tar.bz2 | fgrep ./dev | wc -l
   5181
   
I'm a little confused. Is there supposed to be an additional
installation step to populate the /dev directory when using
recent stage3 snapshots?

-- 
Grant




             reply	other threads:[~2009-01-21  4:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21  4:04 Grant Edwards [this message]
2009-01-21  5:42 ` [gentoo-user] Re: No /dev entries in recent stage3 snapshots? 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
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='gl66sr$pud$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