On Fri, Jul 10, 2009 at 12:36:02PM -0700, Garrett D'Amore wrote: > Nicolas Williams wrote: > >On Fri, Jul 10, 2009 at 10:40:04AM -0700, Garrett D'Amore wrote: > > > >>I actually wonder if a different approach to this would be better -- say > >>a per-filesystem tunable that enables parsing of symbolic links, then a > >>simple -- *short* -- magic token that activates it. Say @@ or > >>somesuch. (Simpler is better here.) The filesystem tunable would be > >>available for administrators that don't want to use referrals, and have > >>@@ (or whatever the magic token is) references already in their > >>filesystems... > >> > > > >The magic could actually be a special automount map, so that any app > >reading a symlink and traversing it on its own would still get to the > >right object. /ref/<reparse-point-config> > > > That would be a quite elegant design, IMO.
Maybe, but the key thing is that such a map need not be implemented from day 1. By just reserving and using the potential special map mountpoint the option would remain available to do this. Also, I'm not sure that apps that read symlinks should have any expectations that the contents of a symlink will be a filesystem path. Nico --
