> Note that, for a NFSv4 client mount, support for hidden/system could > change somewhere in > the mounted server tree, since for NFSv4 the tree can consist of multiple file > systems of different types. For example: > If an ext2 fs was mounted under a ufs file system, the hidden/system support > would go away when the mount point is crossed into the ext2 subtree. > > So, I think pathconf is the best way to go (and avoids using up flag bits).
That's a compelling reason. Consequence is that pathconf() must then be used on the directory where hidden/system files could be created/expected, and not the mount's root directory. Regards. -- Olivier Certner
signature.asc
Description: This is a digitally signed message part.
