Our users want their home directories on their primary (non-Server) machines. That works — I just specify the workstation’s hostname in Workgroup Manager.
Unfortunately, they also want their data on a secondary drive (say /Volumes/home). When I specify this in Workgroup Manager, it creates /home rather than using /Volumes/home. I tried sharing /Volumes/home via SharePoints, but it didn’t help. I tried making /home a symlink to /Volumes/home, and the system silently unmounted the /Volumes/home!
Is there a way to use volumes other than the boot disk on non-Server systems for network homes?
I think I got bitten by part of https://www.afp548.com/article.php?story=20060303070213402&query=symlink
2. You can’t do any of this with afp. If you want to see an afp server/client combo freak out just try having it follow a symlink. The good news is that you can use SMB or NFS or FTP just fine for this setup, with SMB providing the closest experience to afp. The big problem with this would come from trying to create snapshots of existing legacy data. You would need to re-stream all of it from afp to SMB or otherwise split the forks and meta off with SplitForks so that the clients would be able to see them when they connect. If you want to make a design group unhappy, lose the resource forks off all of their Quark files.
Recent Comments