11–20 of 56 posts
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
OpenBSD was never meant to be a desktop BSD. You should take a look at FreeBSD instead.
They all suffer from the good enough but not mainstream enough problem, i.e. official Nvidia drivers that are not officially supported.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
There is support for kernel threads in the form of a flag on rfork(2). The golang port uses this. The pthreads library is still the shitty userland one though.
OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison.
Configure WPA on OpenBSD: ifconfig nwid wpa wpakey up; dhclient
The equivalent on linux is left as an exercise...
It's still a pretty usable desktop though. The new ACPI support is amazing and a completely new implementation, rather than being built on the reference implementation everyone else used.
> no 802.11n support
That's going to require some work on the 80211 layer.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
> - ancient userland pthread implementation There is support for kernel threads in the form of a flag on rfork(2). The golang port uses this. The pthreads library is still the shitty userland one though. OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison. Configure WPA on OpenBSD: ifconfig nwid wpa wpakey up; dhcl…
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
> - ancient userland pthread implementation There is support for kernel threads in the form of a flag on rfork(2). The golang port uses this. The pthreads library is still the shitty userland one though. OpenBSD is great because the man pages aren't absolute shit like Linux and networking is so much better. Linux wifi drivers are absolute crap in comparison. Configure WPA on OpenBSD: ifconfig nwid wpa wpakey up; dhcl…
The 80211 guy retired so there's little chance of that happening.
Earlier quoted context omitted.
OpenBSD was never meant to be a desktop BSD. You should take a look at FreeBSD instead.
I was just throwing out some desktop-specific things at the end and have no interest in running any BSD as a desktop anymore. They all suffer from the good enough but not mainstream enough problem, i.e. official Nvidia drivers that are not officially supported.
To hell w/ NVidia. If they won't play ball, I'll spend my money on an arguably slightly lesser performing product that is more open.
Though, currently the linux emulation layer in CURRENT has a change that broke the linux Flash binary. I've been flash-free for about 2 weeks now. I can't decide if that's a curse or liberation. Otherwise, I personally think FreeBSD is a mighty fine desktop OS. ZFS is really nice.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
I used to love OpenBSD but I've had to abandon it: - no sendfile implementation to accelerate web servers - ancient userland pthread implementation - worst SMP implementation of any mainstream OS - no unified buffer cache - no working TRIM support - no 802.11n support - video card drivers aging, ~3 years behind mainstream - no adobe flash support / hackarounds The only thing I really miss is PF.
Indeed, being worked on with rthreads.
> - worst SMP implementation of any mainstream OS
There's slow progress to push back the kernel biglock.
> - no unified buffer cache
Very few people have a justifyable need for a synchronous cache between read()/write() and mmap().
> - no working TRIM support
Is available in -current, not sure about this release.
> - video card drivers aging, ~3 years behind mainstream
OpenBSD is doing quite well compared to the other BSDs. Intel and Amd graphic options are supported, depending on chipset, OpenGL works out of the box. KMS is being worked on from what I hear.
Nvidia and Adobe, well... they are a cancer and in a perfect world, would go bankrupt for their behaviour.
My favourite bit from the (as always, impressive) changelog: For additional security, security(8) was rewritten in Perl.