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…
OpenBSD 5.0 Released
21–30 of 56 posts
Re: OpenBSD 5.0 Released
#22I 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…
wpa_passphrase > /etc/wpa_supplicant.conf
wpa_supplicant -i -c/etc/wpa_supplicant.conf -B
dhclient
Everything is easy when you know how to do it.Re: OpenBSD 5.0 Released
#23My favourite bit from the (as always, impressive) changelog: For additional security, security(8) was rewritten in Perl.
That reason seems pretty shallow coming from the OBSD team... How can changing the language make it more secure by itself? Is a rewrite in C the next planned enhancement?
Re: OpenBSD 5.0 Released
#24I 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.
Re: OpenBSD 5.0 Released
#25Earlier 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.
It made for an amazing mailserver last I tried it though. I used 3.4 on an ancient P4 with maybe 256MB of RAM an 8GB hard drive. Turns out that was way more computer than it needs, and it was so stable I began to think of it the same way I think of my router.
Re: OpenBSD 5.0 Released
#26I 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…
For example?
Re: OpenBSD 5.0 Released
#27Earlier 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.
And I don't think the users of other BSDs have much need for 3D acceleration..
Re: OpenBSD 5.0 Released
#28My favourite bit from the (as always, impressive) changelog: For additional security, security(8) was rewritten in Perl.
That reason seems pretty shallow coming from the OBSD team... How can changing the language make it more secure by itself? Is a rewrite in C the next planned enhancement?
Re: OpenBSD 5.0 Released
#29Earlier quoted context omitted.
> - 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…
> Configure WPA on OpenBSD: ifconfig nwid wpa wpakey up; dhclient The equivalent on linux is left as an exercise... wpa_passphrase > /etc/wpa_supplicant.conf wpa_supplicant -i -c/etc/wpa_supplicant.conf -B dhclient Everything is easy when you know how to do it.
On a linux system 'man ifconfig' doesn't even mention iwconfig or wpa_supplicant.
I think that makes it a little easier to learn how to do it.
Re: OpenBSD 5.0 Released
#30Earlier quoted context omitted.
That reason seems pretty shallow coming from the OBSD team... How can changing the language make it more secure by itself? Is a rewrite in C the next planned enhancement?
Is security(8) setuid? perl does a number of things to make setuid Perl scripts more secure than either setuid schell scripts or C programs (cf. taint mode).