From: Ulrich Drepper <drepper@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@digeo.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: utimes/futimes/lutimes syscalls
Date: Fri, 11 Jul 2003 22:22:20 -0700 [thread overview]
Message-ID: <3F0F9B0C.10604@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
With the introduction of the nanosecond fields in struct stat the
utime() syscall is kind of obsolete. It's not possible anymore to
restore the exact access/modification time of a file.
Unix defines the utimes() function for this. It is currently
implementated in glibc on top of the utime() syscall which used to be OK
but isn't anymore today. In addition some systems provide the futimes()
and lutimes() functions which appropriate semantics.
The question: would a patch introducing these syscalls be accepted? If
there are filesystems which store the sub-seconds on disk I think this
is necessary since otherwise all kinds of programs (including archives)
cannot be written correctly. If the sub-seconds only live in memory I
still think it would be good to have the syscalls but it would not be
that urgent.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/D5sS2ijCOnn/RHQRAjhgAJoCHPLGWjvK6VUxVmyJx/MPnwzjeQCggpmy
1qKasu1RgrliP4QA0t9QuUE=
=NQyO
-----END PGP SIGNATURE-----
next reply other threads:[~2003-07-12 5:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-12 5:22 Ulrich Drepper [this message]
2003-07-12 5:37 ` utimes/futimes/lutimes syscalls Ulrich Drepper
2003-07-12 5:57 ` David Mosberger
2003-07-12 6:38 ` Ulrich Drepper
2003-07-12 5:42 ` Andrew Morton
2003-07-14 7:45 ` Nikita Danilov
2003-07-14 12:16 ` Tomas Szepe
2003-07-15 18:31 ` Nikita Danilov
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=3F0F9B0C.10604@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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).