[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Bug with ln?
From: |
Alain Trembleau |
Subject: |
Bug with ln? |
Date: |
Mon, 15 Jan 2001 22:54:35 +0000 |
Hi!
I'm not sure if it is a bug, but the 'ln' command is not working that
way that I expect.
If I do the following:
[ ]$ cd /home/apt
[home/apt]$ ls -l example
-rw-r--r-- 1 apt apt 0 Jan 15 22:45 example
[home/apt]$ mkdir test
[home/apt]$ ln -s example test/example
[home/apt]$ ls -l test/example
lrwxrwxrwx 1 apt apt 7 Jan 15 22:46 test/example ->
example
i.e. because I haven't fully specified the path of the first argument to
ln, 'example', ln assumes that it is in the same directory as the second
argument, and the symbolic link generated is an invalid link.
If I continue the above commands with the following:
[home/apt]$ rm test/example
[home/apt]$ ln -s ./example test/example
[home/apt]$ ls -l test/example
lrwxrwxrwx 1 apt apt 9 Jan 15 22:46 test/example ->
./example
Even this does not give the desired result!
Only 'ln -s /home/apt/example test/example' works.
If this is a bug, I hope it's easy to fix!
Regards
Alain
- Bug with ln?,
Alain Trembleau <=