It lookes like you need some information about the file structure used by Linux.
The highest most possible directory you can have in Linux is / (called root) on its own. From / you have all your main sub directories (e.g. home usr root bin dev boot etc). The correct naming for these are /home /usr /root and so on.
If you were to use the ls -a
command in a terminal (shell) this lists ALL the contents of the directory you are in, even hidden ones.
For example, when in your home directory you might see this:
. .gconf .xinitrc
.. .gconfd .xinitrc.asc
.AbiSuite .gentoo-history .xmms
.RealNetworks_RealMediaSDK_60 .gentoorc Mail
.RealNetworks_RealPlayer_60 .gkrellm bin
.RealNetworks_RealShared_00 .gnome code
.Xauthority .gnome_private doc
.acrobat .gnupg downloads
Notice the . and .. on their own.
These are two special files created in EVERY directory.
refers to the current directory and the ..
refers to the directory above, when in your home directory of /home/umd .. refers to /home.
So, when executing the 'patch' command in your last post, yes you should be in the directory of the source you are compiling (e.g. /home/umd/findutils-4.1) and the patch should be above it (e.g. /home/umd/findutilis-4.1.patch)
For all the packages in the book, as long as you are in the directory of the source you will be okay.
One question, you did create a separate partition, and mounted it correctly for a particular drive before compiling?
The reason why /mnt is used is because you create a folder in there called /mnt/lfs and mount a partition to it, thus installing LFS to drive space on the hard drive independant of the current distro.
qulnxsh is right about installing LFS in /root - it is a bad idea.