On Feb 6, 2008 6:53 AM, Alessandro Corbelli <[EMAIL PROTECTED]> wrote: > > Il giorno mer, 06/02/2008 alle 05.52 -0800, Dan Nicholson ha scritto: > > 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. > > > So you are saying that the correct way to build an LFS 6.3 via jhalfs is > to run the whole jhalfs and at the end, bind /dev from host to lfs and > then change password and install grub? > > Actually I can't install grub because /dev isn't populated. > > If this is the correct way, i'll start over again..
That's right. You don't need to start over, though. Just do the Ch. 6.2 stuff, chroot, and work through Ch. 7 and 8 again (not including building the kernel, it's probably fine). I'm confident that jhalfs is already doing the right thing when it builds the packages. > But is not possibile to have a patched jhalfs that will do this > silently? Maybe, I haven't used jhalfs in a while. If jhalfs is guiding you through the Ch. 7 tasks, then yes, that's a bug in jhalfs. If it's building the packages, finishing, and then telling you to do Ch. 7, then I don't think jhalfs should handle that. There just wouldn't a sane way to setup the chroot, leave the user to do what they need, and then somehow tear down the chroot later. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
