Relative paths in chapter 6

[likemagic@…]

in chapter 6 alot of the code contains relative paths typically ../../lib

This is completely dependant where the source code is located. Needs to be changed to an absolute path to simplify things for new/inexperenced users.

[jim@…]

Run the following command without the source code on the directory ln -sf ../../lib/libz.so.1 /usr/lib/libz.so

What these commands do is create a symlink at /lib, remember it's relative to the file in /usr/lib, so it doesn't matter what directory your in, this will work. If this doesn'tn work on your system, reopen this ticket with some sample data.

Marking as invalid.

[likemagic@…]

Hi,

I do not wish to start a flame war but it tried installing LFS on a box running mandrake 8.1 and failed - what i am doing is trying to get the book updated to be clear up all the areas where it was not clear or took time to work it out. If lfs is to be useful to more than a select few this is essential.

Run the following command without the source code on the directory ln -sf ../../lib/libz.so.1 /usr/lib/libz.so

^{this bit here is a relative path if the person is not in the}

correct directory ie they have not put there source in $LFS/sources as per chapter 3 this WILL NOT work.

unraveling the relative path assuming we are in the source code directory results in

../../lib/libz.so.1

^{is the root dir /}

^{is $LFS/sources}

so why cannot the book just have ln -sf /lib/libz.so.1 /usr/lib/libz.so

[jeremy@…]

In the future, please read the LFS FAQ first!

​http://lfs.linux-phreak.net/faq/#wrong-ln-s-command

When a relative path is used in a "ln" command, it's relative to the link being created, NOT to the current directory. Read the man page for ln, and it will explain this.