On Jul 17, 2013, at 11:21 AM, Al Kossow <aek at bitsavers.org> wrote:
On 7/17/13 7:16 AM, Peter Corlett wrote:
On Wed, Jul 17, 2013 at 09:35:40AM -0400, Steven
Landon wrote:
[...] OS X Dropped support for mounting NFS
shares, [...]
I'm running 10.8.4 and I can assure you that this is most definitely not the
case, as I keep most of my data on real computers and mount them over NFS from
my Mac laptop.
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.
I have a lot of the same problems with migrating Netatalk shares between
various BSD and Linux hosts; the installs of Netatalk tend to have different
AppleDouble schemes set up and so the resource forks end up borked. One of
these days, I really need to make a quick tool to move from one format to
another easily.
FWIW, Netatalk claims to handle the old OS X AppleDouble method as well as
at least two of its own, all of which are generally mutually incompatible.
- Dave