Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Originally posted by sapilas you say in a point in the book you have to mount the /proc ..in order for some programs to work...
well my /proc is already mounted . . cannot remounted, or umounted, so it is ok if for the time use /my_lfs/proc --> /proc
make it a link sto the current /proc ?
is it ok ?
Read the commands in the book again. You don't just mount proc again, you "mount --bind" it, which is totally different from a regular mount. It's like making a copy of a directory (compare it to a hard link (not symlink)).
In order for certain programs to function properly, the proc file
system must be mounted and available from within the chroot'ed
environment as well. It's not a problem to mount the proc file system
(or any other file system for that matter) twice or even more than
If you're still logged in as user "lfs", you should log out and log in
again as user root. The reason for this is simple: only root is
allowed to mount filesystems and to run chroot.
The proc file system is mounted under $LFS/proc by running the
following command. We'll also chown it to user root/group root while
we're at it (the rest of the filesystem is chown'ed to root.root in a
minute when we start with chapter 6).
chown root.root $LFS/proc &&
mount proc $LFS/proc -t proc
sorry I meant to say to try using mount --bind instead of the regular one.
But before you try it: did you type $LFS? Is $LFS set? If $LFS is not a variable, it will be ignored and when you type the command, bash will try to execute this: mount proc /proc -t proc
instead of: mount proc /mnt/lfs/proc -t proc
Perhaps you need to read chapter 2 - about $LFS again.
It tells you to always replace $LFS by the real path, don't type $LFS literally, unless you are 100% sure that the $LFS variable is set. If it's not, you can expect bad things to happen. You could chroot into your host distribution instead of to /mnt/lfs and overwrite your Debian or Redhat or whatever it is with LFS files. It won't go over well and you will probably end up with a busted Linux system that has been renderred unusable.
well the LFS whole setup takes less than 4 hours . . I believe...
with a amd @ 1,53Ghz you are done quite fast.. if yuo have read the whole book once and understand what are you going to do.
TO LFS DEVELOPERS?
Is there any way that you can create a script that runs all the bzip2 -d and tar -xvf commands and then compile each package one by one ? and promt the user for the glibc version and the compatibility FHS issues ?
it will make LFS a few hours setup with no much efford...