First time post here but I've installed 4 different versions of LFS without too much mishap. I think my build method would avoid this problem so I would like to share it with the Support List. Simple really. Just embed the chroot command in a short shell script that includes mount commands to bind the host /dev to $LFS/dev and host / tools to $LFS/tools before the chroot and umount them when chroot returns. I also put /etc/fstab in place before I start building packages. Then you can use commands like mount -a and mount /proc in $LFS/ root/.bash_profile and the corresponding umount commands in $LFS/ root/.bash_logout to automatically put your LFS environment into a complete state whenever you enter the LFS partition and clear up after you when come out again. Regard Richard Russell
On 23/03/09 01:17:45, Dan Tran wrote: > Hello, > > I am a first time user of LFS, and was away from linux related wor > for > quite some time. > > I am now at chroot phase where I managed to wipe out my $LFS/dev > directory which was still bound to the actual /dev > > My system is still functional, i just can not login ::( > > my original host is 32 bit redhat 5.0. > > It would be very appreciate if someone can tell me how to recover my > /dev directory. > > Lesson to learn not to use real system to develop LFS which has > already been warn!!! > > Also, the LFS doc could also give a big warning as well ( ie 6.2.2. > Mounting and Populating /dev ) > > I am using latest development LFS (7.0? ) > > Big thanks ahead > > -Dan > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-support > FAQ: http://www.linuxfromscratch.org/lfs/faq.html > Unsubscribe: See the above information page > > -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
