unexpected behaviour of cp (ext3?)
Code:
cp api.odt ../../../unified I went back there and saw if I messed up something when I gave the path. But everything was correct. Then happened this bizarre stuff. Code:
[root@DER01C doc]# file ../../../unified This is seen on a Fedora 7 machine. Code:
[root@DER01C work]# uname -a |
Quite likely your path '../../../unified' refers to a symbolic link in the filesystem. In this case, the '..' will reference the actual directories, and not the path along the links. You aren't the first to have been bitten by this. To demonstrate what I mean, try the following (this is most revealing if you have a bash prompt using something like 'PS1=[\u@\h \w]':
Code:
mkdir -p /tmp/dir1/dir2/dir3/dir4 --- rod. |
Quote:
Code:
[root@DER01C work]# ls -l unified <edit> After posting this, I did stat on "../../../unified" and then a stat on "/work/unified". They were in fact two different files (Had different inodes). Then I tried to recreate the problem and I suddenly noticed that one of the top directories of the "doc" directory was a link (I have reached doc cd /work/f1/f2/doc. f1 was a link). You were correct theNbomr. Thanks. </edit> |
All times are GMT -5. The time now is 03:17 AM. |