From: erik quanstrom <quanstro@quanstro.net>
To: lucio@proxima.alt.za, 9fans@9fans.net
Subject: Re: [9fans] file creation time
Date: Thu, 22 Jan 2009 13:08:37 -0500 [thread overview]
Message-ID: <7ace5eae935a5132ddb514b35b67539e@quanstro.net> (raw)
In-Reply-To: <6ad3bbac8db808921b373026762db2e6@proxima.alt.za>
On Thu Jan 22 12:54:14 EST 2009, lucio@proxima.alt.za wrote:
> > use the dump, luke. ☺
>
> If there was an easy, foolproof way to scan the dump by filename, I
> presume I could search for the earliest instance and consider that the
> time of creation. Not entirely viable, is it?
it's hard to give a good answer, since i don't
know what the goal is.
> I do wonder why this field was sacrificed in the file system(s) and
> 9P*?
>
> Or am I dreaming and the time of creation is just a figment of my
> imagination?
of course on a worm filesystem, you could say that each
time a file is modified after it has made it to the worm, it
becomes a brand new file. though the qid.path doesn't
track this view. the create time would then differ
from the mtime by as most the time between dumps.
andrey suggests
> history(1)
history doesn't give creation times. it gives the last mtime
before the first dump of the file. the file could be deleted
and recreated many times and you'd never know. (unless
you were to peek at the qid.path.)
but then again, history might be exactly what you're
looking for. it usually is for me.
- erik
next prev parent reply other threads:[~2009-01-22 18:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 17:39 lucio
2009-01-22 17:43 ` erik quanstrom
2009-01-22 17:50 ` lucio
2009-01-22 17:57 ` andrey mirtchovski
2009-01-22 18:08 ` erik quanstrom [this message]
2009-01-22 18:16 ` roger peppe
2009-01-22 18:20 ` lucio
2009-01-22 20:35 ` Charles Forsyth
2009-01-22 18:21 ` erik quanstrom
2009-01-22 19:31 ` Richard Miller
2009-01-22 19:54 ` erik quanstrom
2009-01-22 19:01 ` Charles Forsyth
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=7ace5eae935a5132ddb514b35b67539e@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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;
as well as URLs for NNTP newsgroup(s).