From: Al Viro <viro@zeniv.linux.org.uk>
To: Theodore Ts'o <tytso@mit.edu>
Cc: David Laight <david.laight.linux@gmail.com>,
"Artem S. Tashkinov" <aros@gmx.com>,
linux-ext4@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A syscall for changing birth time
Date: Tue, 11 Mar 2025 04:56:35 +0000 [thread overview]
Message-ID: <20250311045635.GP2023217@ZenIV> (raw)
In-Reply-To: <20250311044935.GD69932@mit.edu>
On Tue, Mar 11, 2025 at 12:49:35AM -0400, Theodore Ts'o wrote:
> This really goes to my question of exactly how useful the file
> creation time concept really is. Perhaps that's why the developers at
> the UC Berkley made ctime be "inode change time", I suspect when they
> authored the BSD Fast File System 42 years ago. Personally, while I
> don't find "change time" to be all that useful --- I find "creation
> time" an order of magnitude *more* useless. :-)
The third timestamp had been introduced in v7 and it had been "change
time" from the very beginning, with incremental backups as stated
rationale in filesys(5). "I'm sure that" from David means "I couldn't
be arsed to check my WAG"...
next prev parent reply other threads:[~2025-03-11 4:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 7:26 A syscall for changing birth time Artem S. Tashkinov
2025-03-10 13:58 ` Theodore Ts'o
2025-03-10 14:11 ` Artem S. Tashkinov
2025-03-10 15:37 ` Theodore Ts'o
2025-03-11 16:08 ` David Sterba
2025-03-11 21:14 ` Theodore Ts'o
2025-03-10 22:12 ` David Laight
2025-03-11 0:31 ` Al Viro
2025-03-11 4:49 ` Theodore Ts'o
2025-03-11 4:56 ` Al Viro [this message]
2025-03-11 17:07 ` Theodore Ts'o
2025-03-11 18:11 ` Al Viro
2025-03-11 20:01 ` David Laight
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=20250311045635.GP2023217@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=aros@gmx.com \
--cc=david.laight.linux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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