Slashdot Mirror
OpenBSD Marches Toward 5.0 Release
badger.foo writes "OpenBSD-current just turned 5.0-beta, providing us a preview of what the upcoming release (slated for November 1st) will look like. Peter Hansteen takes us through the main new features and explains the development process that has consistently turned out high-quality releases on time, every six months for more than a decade."
If it wasn't for the fact that most System Administrators are more comfortable with Linux or Windows (And many of the new ones are not too willing to expand that much on the command line). I would have all my servers running OpenBSD. You get it set it up to do the Job you want and let it work.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
OpenBSD 5.0 will be released in November.
Twice a year releases mean that we knew this back in 1996.
And 5.0 will be just as much a major release as 4.9 was.
If your hardware is older, OpenBSD is a safer environment - if your CPU does not implement the NX bit, OpenBSD manages the same functionality with W^X. Many other memory-handling features make the system safer (malloc with mmap, rather than sbrk, for example), although there can be a performance penalty.
OpenBSD implements privilege separation in many of the daemons of the base system (ftpd, dhcpd, ntpd, sshd), so you can trust them more.
OpenBSD's alternate daemons for well-known protocols (ntpd, smtpd) give you some "security through obscurity," and you also gain flexibility.
There are also custom patches for well-known servers to improve security (apache chroot).
In a number of ways, OpenBSD is the "Reference UNIX Security implementation." Come see why.
Sweet! Does it ship with Pulse Audio?
However there are many people who try to seem smarter than they're, and they might deserve to be made fun of.
Leaving aside the moral debate of when a person deserves mistreatment, what is the value of abusively mocking someone in a public forum? It does not raise the level of discourse to something productive. At the least it's a kind of friction and so energy goes out the window as a kind of heat loss. Maybe it's a kind of turbulence that amplifies the original wobble of stupidity rather than smoothing things back into a laminar flow. Maybe it promotes a culture of antagonism, resulting in rampant friction and turbulence throughout, even in areas where there's small and meaningful/useful disagreement.
From what I can tell, it's an emotionally underdeveloped way of giving in to one's anger urges rather than a well-considered method for advancing discussion and making progress. You could say it retards progress. There are other, more sophisticated, and actually beneficial ways for handling disagreement and coping with people who are patently wrong.
but did you ever figure out why virtualization is a bad hack to prop up crappy software?
Poettering:
"You're not welcome to complain if it's free"
On how the speaker got feedback from various mailing lists/communities:
Poettering: "You didn't ask the right people...next time just ask me, thank you very much."
Poettering:
"I'm sorry your mindset from the 1970s unix is not up-to-date anymore...*booos*...I see, lots of UNIX lovers here...*cheers*
Speaker:
(after talking about hald)
Poettering: "Ok, hald has been deprecated for 2 years, not my fault people still use it."
speaker: Yes, but it's got these limitations, we should get rid of it, do you agree
Poettering: No, when we designed it it was great, it did all these things that could never be done before
speaker: but it never worked
Poettering: you're doing it wrong, it worked great.
The guy interrupted the speaker for the entire talk and then got up and stage after him and took the mic. What an asshole. Completely regardless of whether or not you disagree with the speaker, it's just plain rude to interrupt a talk like that.