Shut Down System at V8.4 LFS

ritik8699 · 08-30-2019, 10:16 AM

I accidentally shut down my system at point 6.9.1 before running below code :-

Code:

CC="gcc -isystem $GCC_INCDIR -isystem /usr/include" ../configure --prefix=/usr --disable-werror --enable-kernel=3.2 --enable-stack-protector=strong libc_cv_slibdir=/lib

After restarting, I am just so confused about what to do and what not to do to resume exactly from where i left off.
Here is what I did :-

- Mounted partitions
- Chrooted using :-

Code:

chroot "$LFS" /tools/bin/env -i \
HOME=/root \
TERM="$TERM" \
PS1='(lfs chroot) \u:\w\$ ' \
PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
/tools/bin/bash --login +h

What else do i need???
How would i know that now I am exactly where i left off??
Sorry for such newbie quetions but it's my first time building LFS.
Thanks in Advance.

hazel · 08-30-2019, 10:39 AM

First thing is to mount all the necessary systems, not just the new partition but the dynamic directories it's going to need (/dev, /proc, /sys, etc.). See section 6.2 for details. Better still, put all this into a permanent script which you can run whenever you need it. For example, here's mine:

Code:

# Script to enter LFS chroot environment
#!/bin/bash

export LFS=/mnt/newlfs
mount /dev/sda9

# Dynamic filesystems 
mount -v --bind /dev $LFS/dev
mount -vt devpts devpts $LFS/dev/pts -o gid=5,mode=620 
mount -vt proc proc $LFS/proc 
mount -vt sysfs sysfs $LFS/sys 
mount -vt tmpfs tmpfs $LFS/run 

# and now chroot...
chroot "$LFS" /tools/bin/env -i  \
     HOME=/root                  \
     TERM="$TERM"                \
     PS1='(lfs chroot) \u:\w\$ ' \
     PATH=/bin:/usr/bin:/sbin:/usr/sbin:/tools/bin \
     /tools/bin/bash --login +h

As you can see, this defines LFS, does all the mounting and then chroots. I keep it in root's home directory so that I can run it whenever I want to do a bit of LFS building. Note that all the mounts have to be done before you chroot. They can't be done from inside the new system.

Then go to /sources and delete the directory you were working in. I assume that is glibc. Delete it completely. Then untar the package and start again. That is a universal rule. Never work in a directory that is partially filled with earlier work.

If you follow these rules, interruptions won't hurt you and you can spread your build over as many sessions as you like.