From: Jamie Lokier <jamie@shareable.org>
To: jw schultz <jw@pegasys.ws>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>
Subject: Re: ReiserFS patch for updating ctimes of renamed files
Date: Tue, 14 Oct 2003 10:29:09 +0100 [thread overview]
Message-ID: <20031014092909.GB24812@mail.shareable.org> (raw)
In-Reply-To: <20031014064924.GP15809@pegasys.ws>
jw schultz wrote:
> Of course if i had designed it in the first place with the
> filesystem semantics that we have now there might be no
> rename system call. Renames would be done by link(oldpath,
> newpath); unlink(oldpath); A sequence that would cause
> ctime to change as a result of nlink changes. A sequence
> that might be appropriate in some cases even inside the
> filesystem code.
Once upon a time, that's how renames were always done.
The rename() system call was added because (a) it provides the
additional atomicity semantic, which link+unlink does not; (b) it is
useful to allow directory renames, but directory hard links are
dangerous so not allowed any more.
-- Jamie
next prev parent reply other threads:[~2003-10-14 9:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 6:05 ReiserFS patch for updating ctimes of renamed files Alex Adriaanse
2003-10-12 7:14 ` jw schultz
2003-10-13 5:49 ` Hans Reiser
[not found] ` <20031013073154.GL8724@pegasys.ws>
2003-10-13 8:45 ` Hans Reiser
2003-10-14 2:37 ` Alex Adriaanse
2003-10-14 6:09 ` Hans Reiser
2003-10-14 6:49 ` jw schultz
2003-10-14 9:29 ` Jamie Lokier [this message]
2003-10-13 10:24 ` Andrew Morton
2003-10-14 6:13 ` Hans Reiser
2003-10-14 6:25 ` Andrew Morton
2003-10-14 6:30 ` Hans Reiser
2003-10-14 6:44 ` Andrew Morton
2003-10-14 7:09 ` jw schultz
2003-10-13 5:32 ` Hans Reiser
[not found] <Gr0H.1ol.5@gated-at.bofh.it>
2003-10-14 6:57 ` Anton Ertl
2003-10-14 8:40 ` Hans Reiser
2003-10-14 14:08 ` Alex Adriaanse
2003-10-25 14:42 ` Alex Adriaanse
[not found] <JIEIIHMANOCFHDAAHBHOMENJDAAA.alex_a@caltech.edu>
[not found] ` <3FBBA8A7.7090802@namesys.com>
[not found] ` <200311201746.15843.vs@namesys.com>
2003-11-23 4:22 ` Alex Adriaanse
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=20031014092909.GB24812@mail.shareable.org \
--to=jamie@shareable.org \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=jw@pegasys.ws \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.