What does /../ mean ?

status1 · 10-04-2006, 07:17 PM

Hello.
I am building lfs 6.0 from the book for the first time an I came across an error
bash: /mnt/lfs/tools/bin/../lib/gcc/i686-pc-linux-gnu/3.4.1/specs: No such file or directory
I was just wondering if anyone knows what does /../ mean in that line ?

FreeDoughnut · 10-04-2006, 07:43 PM

.. always means the directory above it. So /usr/.. would be /. That translates to /mnt/lfs/tools/lib/gcc/i686-pc-linux-gnu/3.4.1/specs

status1 · 10-05-2006, 05:55 PM

Hello,
Thanks for the reply
That makes sense.
I was just wondering what would cause that
Why not just have a normal path /mnt/lfs/tools/lib/gcc/i686-pc-linux-gnu/3.4.1/specs
Why would that need to be translated ?

My concern is that perhaps the new lfs I am building may not be able to translate the path and therefore it throws a No such file or directory
error.
Is that possible ?

spirit receiver · 10-05-2006, 06:07 PM

Quote:

Originally Posted by status1

Why not just have a normal path /mnt/lfs/tools/lib/gcc/i686-pc-linux-gnu/3.4.1/specs

Because this might be a script that doesn't necessarily know the absolute path. Let's say it has /mnt/lfs/tools/bin/ stored in a variable and wants to use the 'sibling' of that directory. Then it's much easier to append ../lib/ instead of modifying the content of the variable.

status1 · 10-05-2006, 06:55 PM

Hello,
Thanks for that answer.

Is it possible that it may cause a No such file or directory error if the program that needs that file doesn't have an absolute path ?

status1 · 10-08-2006, 07:36 AM

Hello,
This is just an update in case anyone is reading this.
The problem has been solved so this is no longer an issue.
The /../ can stay there atleast it's no longer a problem for me
My problem was unrelated