Now I can get the "I have no name!" output when I chroot, but nothing works in bash! Every time I put in a command I get no output and no prompt what-so-ever. Im thinking it's because I had to recompile bash, which pisses me off!!!

Ive spent hours working on this to have to turn right around and start all over, not because of a mistake I made but because of a mistake made in the documentation. Which brings me to question number one...........

1.) How many more documentation errors am I going to run into thats going to force me to turn around and start all over again.....again!???

Does anyone know how to fix this without me having to do all of this over?


Thanks in advance...I gotta take a break!

you are inside the chrooted environment, you have one of the following circumstances:

1) Bash is looking for the programs in /usr/bin/someprogramiwanttofind
2) Bash is looking for the programs in /tools/bin/someprogramiwanttofind

*there are more locations bash looks in, but they are irrelevant as they still point to one of these two problems

Now, to find out what is going out type the following command:

echo $PATH

If what you get back looks something similar to: /sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin. Then this means that you have finished installing the temporary system (or should have!). In this case, you didn't finish installing some things on your new system or you forgot to append /tools/bin to the PATH.

You should make sure /tools/bin or /tools/something is in PATH <-- re-read the LFS environment setup pages for this.
If adding the /tools to the PATH does not solve the problem, then somethings is missing ou need to exit the chrooted environment and find the missing program and install it.

If it /tools is somewhere in there, then your program is not installed in /tools. I would call this worse case, problem could be missing file or badly configured linker (see the pages about ld.conf.so). If you are here, then it may be easier to reinstall the new system, delete the tools directory and reinstall that as well. Unless of course, you are willing to spend time experimenting and learning how to solve your problem as I am very confident that the specific solution will be found by spending a few hours searching the LFS mailing lists archives.

There are a very delicate parts of the installation that deal with switching between the systems and messing up anywhere in there will cause this kind of problem

Im on it! After taking a break I decided to start the process all over again. (Actually Ive done this two or three other times and have corrected mistakes and learned a ton from doing so). This time around things are going a little more smoothly and with the help of you lfs gurus I have made improvements each time in. Im just one step closer to getting this thing up and running like a champ!


Thanks for your help yerp. Wish me luck..Im having a blast