On Feb 6, 2008 3:57 AM, Alessandro Corbelli <[EMAIL PROTECTED]> wrote: > I think i've found the mistake. > > /dev directory is semy-empty! > > # ls -la /dev > crw------- 1 root root 5, 1 5 feb 16:35 console > crw-rw-rw- 1 root root 1, 3 5 feb 16:35 null > -rw-r--r-- 1 root root 21 6 feb 10:21 tty
I don't know what's in /dev/tty, but just remove it. It will always just be a stale, broken device on your root filesystem. Usually, you'll have a tmpfs mounted over /dev, but no good could come from having that there. > How to populate dev? > > Older version says to mount ramfs to /dev and startup udev but with 6.3 > there isn't a section called "populating /dev" This sounds like a jhalfs issue. I think what's happening as that the chroot gets setup properly when building all the packages. After all the packages are built, it tears down all the chroot setup. However, this is when it handles the extra setup, like the root passwd, it just runs the command in the chroot without setting up the devices, etc. I haven't looked closely, though. So, to answer your question, you still mount a tmpfs on /dev. The instructions got refactored a bit, but the info is here in Ch. 6.2: http://www.linuxfromscratch.org/lfs/view/6.3/chapter06/kernfs.html You need that `mount --bind' to use the devices your host setup. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
