> On Oct 3, 2015, at 14:41, Brandon Allbery <allber...@gmail.com> wrote: > > On Sat, Oct 3, 2015 at 2:39 PM, Clemens Lang <c...@macports.org > <mailto:c...@macports.org>> wrote: > > Same thing, but as seen in the 2nd case, no com.apple.rootless attribute, no > > restricted (or hidden) flags. :-) > > Mounts are a nice idea, but not possible without root privileges, and that > leaves > out everybody that uses a user-only installation of MacPorts. So this could > only > be done as an optimization, and I'm not sure it's worth it then. Cache > invalidation would definitely be easier with it, though… > > ...but at some point the NFS server must access the file, in the original > filesystem where all of those exist and will be enforced.
To explain why my trick worked...NFS server doesn't know about execs; at that level, it's just getting file read RPCs. So there's nothing for NFS server to enforce. The client could enforce, but not if the NFS implementation doesn't communicate named attributes (and the NFS protocol doesn't support chflags() flags).
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
