Live data from Hacker News

FreeBSD on a MacBook Pro

gist.github.com

21–30 of 100 posts

Re: FreeBSD on a MacBook Pro

#21
post #5

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)

Re: FreeBSD on a MacBook Pro

#23
post #20

Earlier quoted context omitted.

Random question for you, how does the shell experience on FreeBSD compare to MacOS? Linux?

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.

Re: FreeBSD on a MacBook Pro

#24
post #20

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.

GNU rm (coreutils) vs BSD rm.

Re: FreeBSD on a MacBook Pro

#25

"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.

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?

Re: FreeBSD on a MacBook Pro

#26
post #19

Earlier quoted context omitted.

Which FreeBSD version did you try? I'm just skimming things, but it looks like Adrian Chadd might have updated the relevant driver back in May/June, in time for FreeBSD 11.

If its for the broadcom cards that's probably still a negative. I was running 11-CURRENT up until the release freeze and it never started working. That being said, it wouldn't surprise me if Adrian has it working by now.

Adrian has done a lot of recent work on 11ac in -HEAD, but not anything on BRCM of late.

Re: FreeBSD on a MacBook Pro

#27

> Six years later, it less and less "Just Works", started turning into spyware and nagware, and doesn't need much less maintenance than Linux desktop — at least for my work, which is system administration and software development, probably it is better for the mythical End User person. Work needed to get software I need running is not less obscure than work I'd need to do on Linux or othe Unix-like system.... GUI tha…

Homebrew and a Vagrant managed Linux VM depending on the situation. I'm seriously considering moving to Linux next time I'm switching my work laptop.

Re: FreeBSD on a MacBook Pro

#28
post #20

Earlier quoted context omitted.

Random question for you, how does the shell experience on FreeBSD compare to MacOS? Linux?

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.

Yep. Mostly the same. Hence the reason I question why FreeBSD might be worth it. The overlap of OSX and FreeBSD at the shell is quite great, but you can't run a lot of OSX apps on FreeBSD. I'd venture to guess you could run a lot more FreeBSD apps on OSX.

Re: FreeBSD on a MacBook Pro

#29
post #24

Earlier quoted context omitted.

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.

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.

Re: FreeBSD on a MacBook Pro

#30

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?

No, but there is a port of bhyve using the MacOS hypervisor.framework

https://github.com/mist64/xhyve

Post reply on HN