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 ?

or I better remove temporarily the

/proc proc

line from my fstab and reboot the system....
and then mount it manually to my chroot env ??

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)).

There is no such a bind ??
or am I wrong ?

=====================================

Mounting $LFS/proc file system

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
that.

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

well I checked man 8 mount there is a command --bind . .

but I didn;t find it in the book....

so that;s the solution

use that option in the mount

mount --bind it as root in the linux and then chroot env and the mount will stay there in the new env ?

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.

So, make sure $LFS is set. it is very important.

well to be sure I use /my_lfs/ instead of the $LFS

but I get an errro this specific device does not exists....but strange cause when I type mount I get the list and /proc is there listed...

the problem I think was that I was starting the chroot without the special command .....that is provided...


I reistall everyting to be sure ..but I have two thinks to ask...cause I am during an exam period and have no time to waste searching..

I am at the point that I install the LFS-Bootscripts....

It says the is you like BSD startup scripts just ignore chp7... I was using familiar with slackware's init script....and I heard that those are bsd like. are they ???

if yes then I should skip chp7 to get slackware like init scripts in the chap8..

also is the FHS issues important to follow ? or just ignore them ?

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...

See ALFS http://automated.linuxfromscratch.org