Strange problem, symlinks and parent dirs

2004-12-02 Thread Fabio Tranchitella
Hi folks! I don't know if I'm missing something (if so please don't blame me) but I think there is something wrong with symlinks and parent dirs. Here an example: $ pwd /home/kobold $ mkdir -p dir1/dir2 $ touch dir1/dir2/file $ ln -s dir1/dir2 dir2 $ cd dir2 $ pwd /home/kobold/dir2 $ mv file ..

Re: Strange problem, symlinks and parent dirs

2004-12-02 Thread Cameron Patrick
Fabio Tranchitella wrote: > This is exactly what I was thinking of about this problem, but if run > "cd .." the symlink works as a normal directory, it is transparent. > So my question is: is there any possibility to fix that? Is it a > kernel problem, a pwd issue, a shell issue or what? The fa

Re: Strange problem, symlinks and parent dirs

2004-12-02 Thread Fabio Tranchitella
Il giorno gio, 02-12-2004 alle 11:15 +0100, Christoph Berg ha scritto: > Sure. ".." is resolved by the kernel which doesn't care about the "name" > of your pwd. It just moves the file to the physical .. directory, i.e. > doesn't go the symlinks back. This is exactly what I was thinking of about th

Re: Strange problem, symlinks and parent dirs

2004-12-02 Thread Christoph Berg
Re: Fabio Tranchitella in <[EMAIL PROTECTED]> > $ ln -s dir1/dir2 dir2 > $ cd dir2 > $ pwd > /home/kobold/dir2 > $ mv file .. > > The file is moved into /home/kobold/dir1 instead of /home/kobold > Is this right? IMHO it's confusing for the user. If pwd returns > "/home/kobold/dir2", .. should be r

Strange problem, symlinks and parent dirs

2004-12-02 Thread Fabio Tranchitella
Hi folks! I don't know if I'm missing something (if so please don't blame me) but I think there is something wrong with symlinks and parent dirs. Here an example: $ pwd /home/kobold $ mkdir -p dir1/dir2 $ touch dir1/dir2/file $ ln -s dir1/dir2 dir2 $ cd dir2 $ pwd /home/kobold/dir2 $ mv file ..