On 2009-01-21, Neil Bothwick <n...@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. Anything else is a waste of
> disk space and inodes as the static /dev/devices are hidden as
> soon as udev starts. If the tarball doesn't contain
> /dev/console it is broken, but it is also broken if it
> contains thousands of device entries.
Then all the stage3 tarballs I've ever seen are broken. They
either contain 5000+ entries, or nothing but these:
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
What I do know is that using a stage3 with 5000+ entries allows
you to install using either the normal or quick install
instructions. Using one with just the above /dev entries
causes problems either way -- more so if using the quick
install instructions since there is no step where you mount
udev to /mnt/gentoo/dev.
--
Grant Edwards grante Yow! I'm sitting on my
at SPEED QUEEN ... To me,
visi.com it's ENJOYABLE ... I'm WARM
... I'm VIBRATORY ...
