5 ms·

With a great deal of caution I finally upgraded one of the 5 Macs I own to Catalina over the weekend. First thing I notice is that my NFS mounts no longer work

With a great deal of caution I finally upgraded one of the 5 Macs I own to Catalina over the weekend. First thing I notice is that my NFS mounts no longer work since, they were mounted at a non-standard location. I've shelved further plans to update until I resolve NFS mounts issue using the automounter. Sigh. The apple ecosystem is becoming harder to use. But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose.

K0SM0S 7y ago
> Sigh. The apple ecosystem is becoming harder to use. But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose. So, first off, sincere sympathy. I feel you, I've been there. My current recommendation to people is: whatever you do in your personal life (Apple, Android, Windows, whatever), keep your Apple-related work environment completely segregated — that usually just means one dedicated Mac and the test iOS devices. Do not use any of it for anything else than work. Do not mix a home server with work-Mac-related stuff and personal life. Do not use the same AppleID. Do not mix anything. It's generally a good approach anyway, regardless of one's development platform/target. It then becomes natural to e.g. never worry about NFS and simply use the "recommended" Apple path — like some Thunderbolt drive, or whatever MacOS networks with these days. The downside that it obviously induces additional cost is debatable: - developing for Apple systems usually translates to higher income, and Apple is somewhat "fairly" (at least in their mind) forcing some extra burden of cost on developers, but it's likely marginal for said devs (although hostile to developing markets, at first glance). - work-related machines generally fall under different tax regimes than personal stuff, and while we surely all dabble into the grey area, it's always better to have it 100% legit work or personal but not both. Insurances etc. may care too. So... Yeah. I hope you can segregate and rationalize the work-Mac(s) to follow Apple's best practice (whatever they push as "This is the way" for MacOS).
- eric-hu 7y ago
  > Do not use the same AppleID. I've done what you suggested in this paragraph, and do this as well. It means you can't use a personal iPad with Catalina's Sidecar feature, which just sucks knowing a second monitor is almost right there.
samatman 7y ago
I was debugging issues with Keybase today and ran into a fix, assuming you're trying to mount from the root directory: to create a directory called /newroot, sudo $editor /etc/synthetic.conf and add the word 'newroot' on its own line, then restart.
akeck 7y ago
https://tisgoud.nl/automount-nfs-on-macos/ https://tisgoud.nl/automount-nfs-on-macos/ may help.
pier25 7y ago
> But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose. I was planning on working on a macOS product but I will hold off for a couple of years and see what happens with the platform. Depending on a diva like Apple that introduces breaking changes without notice is a risky business. For example, Cocoa and OpenGL are clearly on its way out but nobody knows how long they will be supported. SwiftUI is probably the way to go but it's not supported by the majority of macOS devices.

K0SM0S 7y ago

> Sigh. The apple ecosystem is becoming harder to use. But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose. So, first off, sincere sympathy. I feel you, I've been there. My current recommendation to people is: whatever you do in your personal life (Apple, Android, Windows, whatever), keep your Apple-related work environment completely segregated — that usually just means one dedicated Mac and the test iOS devices. Do not use any of it for anything else than work. Do not mix a home server with work-Mac-related stuff and personal life. Do not use the same AppleID. Do not mix anything. It's generally a good approach anyway, regardless of one's development platform/target. It then becomes natural to e.g. never worry about NFS and simply use the "recommended" Apple path — like some Thunderbolt drive, or whatever MacOS networks with these days. The downside that it obviously induces additional cost is debatable: - developing for Apple systems usually translates to higher income, and Apple is somewhat "fairly" (at least in their mind) forcing some extra burden of cost on developers, but it's likely marginal for said devs (although hostile to developing markets, at first glance). - work-related machines generally fall under different tax regimes than personal stuff, and while we surely all dabble into the grey area, it's always better to have it 100% legit work or personal but not both. Insurances etc. may care too. So... Yeah. I hope you can segregate and rationalize the work-Mac(s) to follow Apple's best practice (whatever they push as "This is the way" for MacOS).

eric-hu 7y ago
> Do not use the same AppleID. I've done what you suggested in this paragraph, and do this as well. It means you can't use a personal iPad with Catalina's Sidecar feature, which just sucks knowing a second monitor is almost right there.

samatman 7y ago

I was debugging issues with Keybase today and ran into a fix, assuming you're trying to mount from the root directory: to create a directory called /newroot, sudo $editor /etc/synthetic.conf and add the word 'newroot' on its own line, then restart.

akeck 7y ago

https://tisgoud.nl/automount-nfs-on-macos/ https://tisgoud.nl/automount-nfs-on-macos/ may help.

pier25 7y ago

> But I really have no choice I do a lot of iOS and MacOS development, and its the only platform I can use for that purpose. I was planning on working on a macOS product but I will hold off for a couple of years and see what happens with the platform. Depending on a diva like Apple that introduces breaking changes without notice is a risky business. For example, Cocoa and OpenGL are clearly on its way out but nobody knows how long they will be supported. SwiftUI is probably the way to go but it's not supported by the majority of macOS devices.