Each maintains its own set of user and group id numbers and passwords and each manages authentication and authorization in a vacuum. The same is true for all of the other UNIX systems commonly found in home networks (routers, NAS arrays, etc).
Mac OS X is a UNIX system, but it’s not a managed one like Sun imagined. This is not how most home networks are configured. NIS managed authentication and NFS trusted it for authorization. And your login credentials were checked by a central server no matter where you logged in. If you were user 1234 on one system, you were that on all systems. One protocol they particularly liked was NIS/yp, which shared user accounts and managed security between systems. Sun Microsystems, creator of NFS, expected it would be used in well-administered networks as one component of a whole fleet of network protocols. NFS is a very old protocol created for a very different circumstance. On to NFS! NFS Wasn’t Designed For Home Networks But transfers were still running under 12 MB/s even without the CPU pegged. An old trick for that old dog was to lower the log level to 0 in /etc/samba/smb.conf and this did help. Sure enough, the CPU was pegged at 100% the whole time my transfer was in process.
I was getting less than 10 MB/s so the transfer would take more than two days! Luckily, I rooted the Iomega years ago and was able to get inside and take a look. Yes, that works, except that the Iomega is so underpowered and slow. The easiest option was just sharing the ix4 volume using CIFS ( yes, CIFS). But I got it all working! Here’s the story. This lead me back to my 1990’s nightmares, setting up exports and trying to match ID’s. I tried tuning it but gave up and turned to NFS.
But I needed to make either CIFS or NFS work in my special circumstance thanks to that old Iomega.įirst I tried CIFS since it was already configured, but it was too slow.
Do not want.įrankly, SMB2 (or the newer SMB3) is the best NAS protocol for modern devices thanks to solid support from Microsoft, Apple, and Samba.