public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Driscoll <fenris@ulfheim.net>
To: Martin Rode <martin.rode@zeroscale.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: cp fails in this symlink case, kernel 2.4.25, reiserfs + ext2
Date: Thu, 8 Apr 2004 15:17:48 -0600	[thread overview]
Message-ID: <200404081517.48243.fenris@ulfheim.net> (raw)
In-Reply-To: <1081410996.3770.1405.camel@marge.pf-berlin.de>

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

      parent reply	other threads:[~2004-04-08 21:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-07 17:35 cp fails in this symlink case, kernel 2.4.25, reiserfs + ext2 Martin Rode
2004-04-07 19:16 ` Dave Kleikamp
2004-04-08  7:56   ` Martin Rode
2004-04-08  9:24     ` Andreas Schwab
2004-04-10 19:52       ` Andries Brouwer
2004-04-08 21:17     ` Michael Driscoll [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200404081517.48243.fenris@ulfheim.net \
    --to=fenris@ulfheim.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.rode@zeroscale.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox