From: Hans Reiser <reiser@namesys.com>
To: Alex Adriaanse <alex_a@caltech.edu>
Cc: jw schultz <jw@pegasys.ws>,
Linux Kernel Mailing List <Linux-Kernel@Vger.Kernel.ORG>,
vs@namesys.com
Subject: Re: ReiserFS patch for updating ctimes of renamed files
Date: Mon, 13 Oct 2003 12:45:58 +0400 [thread overview]
Message-ID: <3F8A6646.3070206@namesys.com> (raw)
In-Reply-To: <20031013073154.GL8724@pegasys.ws>
Alex, are you convinced by jw? (I think I am.) Would you be willing to
submit a patch for tar instead?
Hans
jw schultz wrote:
>On Mon, Oct 13, 2003 at 09:49:20AM +0400, Hans Reiser wrote:
>
>
> In theory it is cleaner and purer to do it the way we did. In practice,
>
>>Alex's problem seems like a real one, and I don't know how hard it is to
>>change tar to do the right thing. We'll discuss it in a small seminar
>>today.
>>
>>
>
>Updating ctime does seem messy and a bit irrelevant for the
>atomic rename. You are modifying the directories not the
>fricken file. This isn't DOS! But it would seem he does
>indeed have an issue although i'm not sure what. I've never
>used the listed-incremental option of tar and since the
>manpage is incomplete <rant deleted> i don't know what it
>actually does. However, i have found the use of ctime to be
>terribly unreliable for file management and given what the
>standards have to say on the issue it sounds like tar is
>being abused or has a bug.
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-10-13 8:46 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 [this message]
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
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=3F8A6646.3070206@namesys.com \
--to=reiser@namesys.com \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=alex_a@caltech.edu \
--cc=jw@pegasys.ws \
--cc=vs@namesys.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