Re: Inode modification time (ctime)
- From: Ceri Davies <ceri_usenet@xxxxxxxxxxxxx>
- Date: Mon, 30 Apr 2007 18:46:02 GMT
On 2007-04-30, Tim Bradshaw <tfb+google@xxxxxxxx> wrote:
On Apr 30, 2:08 pm, Ceri Davies <ceri_use...@xxxxxxxxxxxxx> wrote:
On 2007-04-30, Daniel Rock <v200...@xxxxxxxxxxx> wrote:
No. That timestamp is maintained by the kernel (or filesystem) code
internally. You can only set atime and mtime (via the utimes(2) syscall).
One begs to differ.
# fsdb -o w /dev/dsk/c0t0d0s5
Well, you can obviously do anything if you allow access to the disk
directly. I'm guessing the question the person meant to ask was "can
you change it via filesystem-related calls" not "can you change it by
writing bits onto the disk" :-)
I'd read it (in conjunction with similar-ish posts by the same author)
in an audit context, hence my answer :)
Ceri
--
That must be wonderful! I don't understand it at all.
-- Moliere
.
- Follow-Ups:
- Re: Inode modification time (ctime)
- From: Tim Bradshaw
- Re: Inode modification time (ctime)
- References:
- Inode modification time (ctime)
- From: manik
- Re: Inode modification time (ctime)
- From: Ceri Davies
- Re: Inode modification time (ctime)
- From: Daniel Rock
- Re: Inode modification time (ctime)
- From: Ceri Davies
- Re: Inode modification time (ctime)
- From: Tim Bradshaw
- Inode modification time (ctime)
- Prev by Date: Re: Install on x86 Complaints
- Next by Date: Re: Inode modification time (ctime)
- Previous by thread: Re: Inode modification time (ctime)
- Next by thread: Re: Inode modification time (ctime)
- Index(es):
Relevant Pages
|