|
|
Subscribe / Log in / New account

Filesystem-oriented flags: sad, messy and not going away

Filesystem-oriented flags: sad, messy and not going away

Posted Mar 17, 2020 18:42 UTC (Tue) by ale2018 (guest, #128727)
Parent article: Filesystem-oriented flags: sad, messy and not going away

I would have said that the situation would look less messy if similar flags were set at the same bit. Having 64-bit flags seems to allow it. Hmm...

/usr/include/linux/fcntl.h:#define AT_SYMLINK_NOFOLLOW	0x100   /* Do not follow symbolic links.  */
/usr/include/asm-generic/fcntl.h:#define O_NOFOLLOW	00400000	/* don't follow links */
/usr/include/x86_64-linux-gnu/bits/fcntl-linux.h:# define AT_SYMLINK_NOFOLLOW	0x100	/* Do not follow symbolic links.  */
/usr/include/x86_64-linux-gnu/sys/mount.h:  UMOUNT_NOFOLLOW = 8		/* Don't follow symlink on umount.  */


to post comments

Filesystem-oriented flags: sad, messy and not going away

Posted Mar 20, 2020 12:43 UTC (Fri) by draco (subscriber, #1792) [Link]

If they weren't done that way from the start, then that's an ABI change, which isn't allowed.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds