zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Extract CTIME in zsh 4.2.3?
Date: Mon, 22 Aug 2005 15:21:40 +0000	[thread overview]
Message-ID: <1050822152140.ZM7412@candle.brasslantern.com> (raw)
In-Reply-To: <16D53E3C-D453-414D-AB6C-3280FF5573CF@tntluoma.com>

On Aug 22,  1:27am, Timothy Luoma wrote:
}
} I've found a solution, but this will only work with Tiger (Mac OS X  
} version 10.4.x)...
} 
} kMDItemFSCreationDate            The date an item's file was created.

In other words, what you're looking for is some record of the inode
creation time, rather than the inode change time which is what the
stat ctime refers to.

Unfortunately this information simply does not exist on many kinds of
filesystems for OSs whose names have an N in the middle and an X at
the end.  (If I write such an OS sometime, I'll call it ANIMAX.  You
read it here first.)
 
} If there's a more portable way to get this to work, I'd like to learn  
} about it, but this will work for now.

On filesystems derived (as in code was taken, not just inspired by like
the linux ext filesystems) from BSD's FFS, I *think* you can get this
with "ffsinfo -i N" where N is the inode number (which you have to get
some other way, e.g. with stat).  It's called the "birth time".  Please
note, though, that I may be entirely wrong -- the man page for ffsinfo
doesn't say what data is dumped, and I don't have a BSDish system handy
to try it.


  reply	other threads:[~2005-08-22 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 20:01 Timothy Luoma
2005-08-21 20:11 ` Shawn Halpenny
2005-08-22  4:44   ` Timothy Luoma
2005-08-22  5:27   ` Timothy Luoma
2005-08-22 15:21     ` Bart Schaefer [this message]
2005-08-22 18:44       ` SOLVED (more or less) " Timothy Luoma
2005-08-22 15:24     ` Shawn Halpenny
2005-08-22 15:35       ` DervishD
2011-07-26 15:24         ` skullnobrains

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=1050822152140.ZM7412@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).