| 1 |
On 2009-01-21, Grant Edwards <grante@××××.com> wrote: |
| 2 |
|
| 3 |
> I noticed the same thing in the install I did a few days ago. |
| 4 |
> Later in that install grub failed to install and after |
| 5 |
> rebooting, my /dev directory was missing just about everything. |
| 6 |
> |
| 7 |
> Here's the /dev directory in the chroot'ed environment I got |
| 8 |
> using stage3-i686-20090114.tar.bz2: |
| 9 |
> |
| 10 |
> livecd linux # ls -l /dev |
| 11 |
> total 12 |
| 12 |
> lrwxrwxrwx 1 root root 15 Jan 20 21:30 MAKEDEV -> ../sbin/MAKEDEV |
| 13 |
> -rw-r--r-- 1 root root 75 Jan 20 21:49 null |
| 14 |
> drwxr-xr-x 2 root root 4096 Jan 13 19:29 pts |
| 15 |
> drwxr-xr-x 2 root root 4096 Jan 13 19:29 shm |
| 16 |
|
| 17 |
It looks like stage3-i686-20090114.tar.bz2 is broken. |
| 18 |
|
| 19 |
The stage3 tar files for the previous two weeks are missing |
| 20 |
(the DIGEST and CONTENTS files are on the mirrors, but no |
| 21 |
tar.bz2). |
| 22 |
|
| 23 |
stage3-i686-20081224.tar.bz2 seems to have the proper /dev |
| 24 |
entries. |
| 25 |
|
| 26 |
> I'm a little confused. Is there supposed to be an additional |
| 27 |
> installation step to populate the /dev directory when using |
| 28 |
> recent stage3 snapshots? |
| 29 |
|
| 30 |
I guess the additional step is to not use a broken stage3 |
| 31 |
tarball. |
| 32 |
|
| 33 |
-- |
| 34 |
Grant |
Archives