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 18:11:54 +0000 [thread overview]
Message-ID: <20250311181154.GS2023217@ZenIV> (raw)
In-Reply-To: <20250311170725.GE8837@mit.edu>
On Tue, Mar 11, 2025 at 01:07:25PM -0400, Theodore Ts'o wrote:
> I actually pulled down the V7 sources and there was a comment in
> /usr/sys/h/ino.h which has a comment around the on-disk inode stating
> "creation time" (see below). These comments are also there up to
> 3BSD, and changed to "inode change time" in the BSD 4.2 sources,
> probably coincident with the BSD Fast File System implementation.
Ken Thompson is at google these days - might be interesting to ask if
there was a point between v6 and v7 where it was used as 'creation
time'.
https://www.tuhs.org/Archive/Documentation/Papers/BSTJ/bstj57-6-1905.pdf
looks like a reference to 'creation time' in Apr 78, and man/man5/filsys.5
is Jan 79 (already matching actual behaviour of released v7).
I wonder if anything of Interdata 8/32 port survives...
next prev parent reply other threads:[~2025-03-11 18:11 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
2025-03-11 17:07 ` Theodore Ts'o
2025-03-11 18:11 ` Al Viro [this message]
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=20250311181154.GS2023217@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