NeXT Networking

Are there any magic flags that need to be set for NFS to correctly handle legacy app resource forks? I managed to screw myself trying to recover from an rsync backup from 10.4 to a FreeBSD NFS server and having what was copied with rsync -avX create a backup that can't be interpreted correctly on the 10.4 system (all of the resource forks are gone as far as 10.4 is concerned). There is also the problem where there are several incompatible schemes for storing resource forks (some systems append ._ others create an .AppleDouble directory) leaving trails of invisible cruft as files were backed up from system to system. This is a nightmare for backup migration. I'm having to go through every backup that was ever made from MacOS to Unix to identify if the apps have had their resource forks screwed up and either put them back together or purge them.