This looks very cool but I haven't quite got my head around it completely yet.
What happens if open(2) is called with O_NOFOLLOW set on one of these reparse points ? (Please answer for ZFS local access, NFS and CIFS). > One of the main goals in this context has > been the ability to use existing utilities for backup/restore > and also ZFS send/receive without having to modify them to > know how to deal with reparse points. So why not just a system attribute to store the whole thing ? Particularly since it is required to store a system attribute to distinguish a reparse point from a normal symlink anyway. Also if we do end up adding BSD magic link support for the link types they have can a symlink link still have reparse data in it ? -- Darren J Moffat
