31–40 of 100 posts
> back then I grew tired of Linux desktop (which is going to be MASSIVE NEXT YEAR, at least since 2001) The snark was really unnecessary.
I agree, I've been running Arch Linux on my MBP Retina for 2+ years now almost without problems. I bet if the OP tried Linux, they'd be absolutely fine.
Some months ago I got FreeBSD running in a Macbook Air, and surprisingly the UEFI boot worked out of the box. I say surprisingly because when I tried, the Linux efiboot didn't work, the only way to boot linux was through GRUB. I had almost everything working (Audio, suspend on close, i3 or gnome) but never got the wifi to work, I even tethered from my android phone to the Macbook and it worked very good. But in the e…
at least for Ubuntu on a 2013 MBP I had to install non-free wifi, everything else Just Worked (tm)
Earlier quoted context omitted.
GNU rm (coreutils) vs BSD rm.
I will never get used to the trailing slash on source arguments in BSD cp (that copies directory contents rather than the directory itself)! The first thing I do on an OS X machine is install GNU coreutils.
Some months ago I got FreeBSD running in a Macbook Air, and surprisingly the UEFI boot worked out of the box. I say surprisingly because when I tried, the Linux efiboot didn't work, the only way to boot linux was through GRUB. I had almost everything working (Audio, suspend on close, i3 or gnome) but never got the wifi to work, I even tethered from my android phone to the Macbook and it worked very good. But in the e…
ever considered using a supported wifi usb?
Earlier quoted context omitted.
at least for Ubuntu on a 2013 MBP I had to install non-free wifi, everything else Just Worked (tm)
How much battery life do you get from this configuration? macOS is optimized for power. FreeBSD not so much, I believe.
Earlier quoted context omitted.
Not claiming to be knowledgeable about OS X internals, but... it ships with a hypervisor now? Is it at all similar to BSD jails?
No, but there is a port of bhyve using the MacOS hypervisor.framework https://github.com/mist64/xhyve
Earlier quoted context omitted.
A shell is a shell for the most part. The details can be a bit different (like your $PATH), but otherwise its largely the same.
try rm -rf somedir/ vs rm somedir/ -rf Linux (the former) allows me to be lazy while MacOS (the latter) forces me to hit crtl-a and insert -rf.
"using a custom [FreeBSD] kernel seems tricky in a VMWare/VirtualBox VM" This flipped a set-once bit, making the rest of the article essentially unreadable due to zero confidence in the writer's technical skill. Also, the lack of "late 2011" in the title makes it pretty misleading.
So the author really enjoys debugging boot problems, but a custom kernel in a VM is just too tricky? Is there something I'm missing that makes that way harder than debugging dual boot?
Earlier quoted context omitted.
I thought the exact same thing. It's trivially simple to run custom kernels. Further, with currentish versions of OSX, you don't even need VMware/VB. The built-in hypervisor works good enough without crash prone kexts like in the alternative in my experience. Not sure if you read the rest of the article, but it didn't do much to instill technical competence after that point either.
Not claiming to be knowledgeable about OS X internals, but... it ships with a hypervisor now? Is it at all similar to BSD jails?