Re: *at syscalls for xattrs?

Al Viro
2007-07-15T22:23:36Z

On Sun, Jul 15, 2007 at 02:13:21PM -0700, Nicholas Miell wrote:
>
> I suspect he was asking for
>
> int getxattrat(int fd, const char *path, const char *name, void *value,
> size_t size, int flags)
> int setxattrat(int fd, const char *path, const char *name, void *value,
> size_t size, int xattrflags, int atflags)
>
> rather than the ability to access xattrs as files.

Just one question: what the bleeding hell for? Not that the rest of
..at() family made any damn sense as an interface...

> > > 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?
>
> Solaris compatibility.

"Sun having no taste whatsoever"