Hello,It sounds to me like /dev wasn't bind mounted to $LFS/dev before you entered chroot...AlanBind mounted?! What do you mean?Read the book here: http://www.linuxfromscratch.org/lfs/view/stable/chapter06/kernfs.html section 6.22.You need to repeat the page's commands EVERY time you restart your build (if you reboot the host) and check each time you leave and re-enter chroot...Al
Well, I've been following the LFS 6.1.1 book, and the section on virtual kernel file systems says:
==================================================================Various file systems exported by the kernel are used to communicate to and from the kernel itself. These file systems are virtual in that no disk space is used for them. The content of the file systems resides in memory.
Begin by creating directories onto which the file systems will be mounted:
mkdir -pv $LFS/{proc,sys}Now mount the file systems:
mount -vt proc proc $LFS/proc
mount -vt sysfs sysfs $LFS/sysRemember that if for any reason you
stop working on the LFS system and start again later, it is
important to check that these file systems are mounted again
before entering the chroot environment.
Additional file systems will soon be mounted from within the chroot environment. To keep the host up to date, perform a "fake mount" for each of these now:
mount -vft tmpfs tmpfs $LFS/dev mount -vft tmpfs tmpfs $LFS/dev/shmmount -vft devpts -o gid=4,mode=620 devpts $LFS/dev/pts==================================================================Bind mounting is not mentioned here, so I guess it is not needed. Furthermore, GRUB 0.96 DOES detect my HDD when I build LFS 6.1.1 wihtout package users.
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
