Well, I used the word convenience for a reason. I have a MBP running Linux as a server, and it was fiddly to set up correctly. I didn't mind too much, but on macOS you've got none of that.
Catering for edge cases like; when closing lid, it should not go to sleep, with external drive connected and mounted, it won't boot if that somehow disappears, Apple remote cannot easily be disabled (there's one used in the room, and it's picked up by the laptop constantly).
I also have occasional issues where the trackpad stops working after a period, and requires a reboot to fix. More of an X issue I believe.
with external drive connected and mounted, it won't boot if that somehow disappears
Couple ideas, for what little they may be worth. Grub might be installed on the wrong drive. Or, if you’re getting past grub, look up systemd’s nofail option for /etc/fstab.
I remember what it was now, I had mounted in fstab, but using the device path (e.g. /dev/sdb1) instead of the UUID of the disk. The device path seems to occasionally change (which is bizarre as it is the only device connected). Using a UUID does the trick. But it was just an example of many minor details that needed to be fiddled with in order to create a 24/7 laptop server. I don't mind - it's part of the fun I guess, but I'm just waiting for the next edge case.
> But MacOS does handle low memory conditions much better than Windows does.
Interesting, my work machine runs a linux vm on a windows 10 host. It regularly uses 95 to 96% of my 16GB RAM. When this happens Linux grinds to a halt yet Programs running on Windows are still usable. MacOS must be amazing,
