Ask HN: Mojave, anything developers should know about before upgrading?
From what I've seen around the web, this upgrade seems less problematic than previous years, but has anyone spotted any gotchas that other developers could do with knowing about before upgrading?
Very brave - I tend to wait until at least the first point release (so, 10.14.1) or later before taking the plunge. I'd run brew doctor afterwards for sure...
tl;dr: Mojave blocks the VBoxDrv.kext <5.3 kernel extension from loading because "it will panic the machine if allowed to load", and it's up to Oracle to patch on version >=5.3 (current latest is 5.2.18)
Systems that depend on VirtualBox such as Vagrant don't work either.
Downloading it so.. I hope not but Apple updates tend to cause problems rather than solving them, also upgrading Fedora at the same time which may turn out to be dumb, fingers crossed.
tl;dr: Mojave blocks the VBoxDrv.kext <5.3 kernel extension from loading because "it will panic the machine if allowed to load", and it's up to Oracle to patch on version >=5.3 (current latest is 5.2.18)
Systems that depend on VirtualBox such as Vagrant don't work either.
Some guy has posted a workaround but it involves disabling the SIP, proceed at your own risk: https://silvae86.github.io/sysadmin/mojave/beta/vagrant/virt...
Had to reinstall Xcode command line tools after the upgrade finished.
I did run `brew doctor && brew prune`
defaults -currentHost write -globalDomain AppleFontSmoothing -int 3
defaults write -g CGFontRenderingFontSmoothingDisabled -bool false