From: Al Viro <viro@ftp.linux.org.uk>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: linux-fsdevel@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: *at syscalls for xattrs?
Date: Sun, 15 Jul 2007 21:53:13 +0100 [thread overview]
Message-ID: <20070715205313.GE21668@ftp.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0707132228460.25352@fbirervta.pbzchgretzou.qr>
On Sun, Jul 15, 2007 at 09:46:27PM +0200, Jan Engelhardt wrote:
> Hi,
>
>
> recently, the family of *at() syscalls and functions (openat, fstatat,
> etc.) have been added to Linux and Glibc, respectively.
> In short: I am missing xattr at functions :)
No. They are not fscking forks. They are almost as revolting, but
not quite on the same level.
> BTW, why is fstatat called fstatat and not statat? (Same goes for
> futimesat.) It does not take a file descriptor for the file argument.
> Otherwise we'd also need fopenat/funlinkat, etc. Any reasons?
Ulrich having an odd taste?
next prev parent reply other threads:[~2007-07-15 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-15 19:46 *at syscalls for xattrs? Jan Engelhardt
2007-07-15 20:53 ` Al Viro [this message]
2007-07-15 21:13 ` Nicholas Miell
2007-07-15 22:23 ` Al Viro
2007-07-15 23:09 ` H. Peter Anvin
2007-07-16 7:56 ` Jan Engelhardt
2007-07-16 8:04 ` Al Viro
2007-07-16 8:30 ` Jeremy Fitzhardinge
2007-07-16 9:05 ` Miklos Szeredi
2007-07-16 9:33 ` H. Peter Anvin
2007-07-16 9:47 ` Jeff Garzik
2007-07-16 17:57 ` H. Peter Anvin
2007-07-16 20:03 ` Jeff Garzik
2007-07-16 20:40 ` H. Peter Anvin
2007-07-16 9:12 ` Andreas Schwab
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=20070715205313.GE21668@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=jengelh@computergmbh.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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