From: Michael Driscoll <fenris@ulfheim.net>
Organization: FFW/CO
To: Martin Rode <martin.rode@zeroscale.com>
Subject: Re: cp fails in this symlink case, kernel 2.4.25, reiserfs + ext2
Date: Thu, 8 Apr 2004 15:17:48 -0600
User-Agent: KMail/1.6.1
Cc: linux-kernel <linux-kernel@vger.kernel.org>
References: <1081359310.1212.537.camel@marge.pf-berlin.de> <1081365374.11164.24.camel@shaggy.austin.ibm.com> <1081410996.3770.1405.camel@marge.pf-berlin.de>
In-Reply-To: <1081410996.3770.1405.camel@marge.pf-berlin.de>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200404081517.48243.fenris@ulfheim.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1041
Lines: 27

On Thursday 08 April 2004 01:56, Martin Rode wrote:
> On Wed, 2004-04-07 at 21:16, Dave Kleikamp wrote:
> > When you cd to alpha/beta, your current directory is really
> > .../tmp/bug/beta.  Your shell may remember that you got there through
> > the symlink in alpha, but cp will follow .., which is really bug.
>
> Bug in "cp", "bash" or in the kernel fs-layer?
>
> Martin

Call it a bug in POSIX, if anything ;)

Remember that '..' is a directory entry in the filesystem, not a construct of 
your shell.  Specifically, it is a pointer to the parent directory of the 
directory in which it is found.

Usually /a/b/../c is the same as a/c, but not if /a/b is a symlink to /d as in 
this case.

-- 
Michael Driscoll, fenris@ulfheim.net
"A noble spirit embiggens the smallest man" -- J. Springfield
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/