| 1 |
2009/1/21 Grant Edwards <grante@××××.com> |
| 2 |
|
| 3 |
> On 2009-01-21, Dirk Heinrichs <dirk.heinrichs.ext@×××.com> wrote: |
| 4 |
> > Am Mittwoch, den 21.01.2009, 04:04 +0000 schrieb ext Grant Edwards: |
| 5 |
> > |
| 6 |
> >> I'm a little confused. Is there supposed to be an additional |
| 7 |
> >> installation step to populate the /dev directory when using |
| 8 |
> >> recent stage3 snapshots? |
| 9 |
> > |
| 10 |
> > One usually bind-mounts /dev, /proc and /sys into the chroot, like |
| 11 |
> > |
| 12 |
> > mount --bind /dev /newinstall/dev # dito for /proc, /sys |
| 13 |
> > chroot /newinstall |
| 14 |
> |
| 15 |
> |
| 16 |
> > If this isn't documented, you should file a bug. |
| 17 |
> |
| 18 |
> That's docuemented in the "normal" install doc, but not in the |
| 19 |
> quick install doc. |
| 20 |
> |
| 21 |
> But, that doesn't really solve the problem, since after a |
| 22 |
> reboot the /dev directory will be empty again and you end up |
| 23 |
> with problems such as no console during startup. |
| 24 |
> |
| 25 |
> -- |
| 26 |
> Grant Edwards grante Yow! RELATIVES!! |
| 27 |
> at |
| 28 |
> visi.com |
| 29 |
> |
| 30 |
> |
| 31 |
> |
| 32 |
IIRC thats because /dev should be populated on startup by udev so i would |
| 33 |
check that udev is installed and working properly, if you use openrc then |
| 34 |
this could be the cause as openrc now starts udev through normal scripts i |
| 35 |
think, sometimes on upgrade from baselayout 1 they may not be automatically |
| 36 |
added to the right runlevels. |
| 37 |
|
| 38 |
- Nick |
Archives