On Sun, 2007-07-15 at 21:53 +0100, Al Viro wrote: > 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. 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. > > 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. -- Nicholas Miell <nmiell@xxxxxxxxxxx> - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
