Slashdot Mirror
BSD Interview Roundup
Some anonymous readers wrote in to let us know about a couple of different interviews in the OpenBSD and NetBSD communities. O'Reilly's ONLamp has an interview with OpenBSD's Marc Espie, who maintains a good share of OpenBSD's build tools, as well as having made numerous contributions to the project. OSDN's own NewsForge also has a interview with NetBSD's Luke Mewburn of the NetBSD Core Group.
Open, their code is audited regularly, Net is more focused on the portability. That's why they say Open is secure and Net can run on a toaster.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
Needless to say, I had our quad Xeons back running OpenBSD by the end of the week. Gerbil is back on its way to another glorious 3 years of uptime.
.gov and .mil sites and when was the last time the USAF donated a foreign software project $2M US?
OpenBSD on Quad anything is silly at the moment.
OpenBSD is known to be used at the Pentagon and various other
OpenBSD has a security track record that no other network operating system has ever matched.
FreeBSD has phenominal stability and incredible SMP performance is fast coming to a stable release.
NetBSD runs on everything and managed to beat Linux 2.6 scheduler performance (2 years in the making) with just 2 weeks of coding to "catch up".
The BSD's are complete systems and if you ever use one, you'll know why we BSD users value that. The best part is, the BSD's are able to share code amongst themselves. When NetBSD ports to an architecture which interests some OpenBSD developer, that quickly gets ported to OpenBSD. When OpenBSD finds holes, NetBSD and FreeBSD benefit not only from the heads-up but often from a patch which either applies cleanly, or is trivial to modify.
With ProPolice, OpenBSD are now finding lots of holes.
I challenge every person out there who honestly beleives that BSD is dying, to download OpenBSD 3.5 when it comes out. Read the FAQ, read the afterboot man page, use apropos with some level of intelligence and read the man pages, search Google groups and as a last resort ask questions on the OpenBSD mailing lists.
Here's a tip, SCO is dying and they want Linux to die too. Meanwhile, after already surviving a legal battle, BSD is thriving with mature developers who really know their stuff.
OpenBSD is far from a terrible choice for servers in general, except for one class; SMP boxes. Currently, OpenBSD has no SMP support, and although it is being worked on, it won't be out for at least another year, it will be for i386 boxes only, and it will be of a "Big Giant Lock" type of SMP, where if one kernel process holds the BGL, no other kernel processes will be able to run on any of the computer's CPUs. OpenBSD also has no kernel threading ATM, making it less optimal for really intensive tasks.
NetBSD - we just don't make a hype out of it.
NetBSD - secure OF COURSE!
- Hubert
As /. rejected story about this, perhaps at least people, who read messages here can read this...
http://pkgsrcCon.org , the first pkgsrc conference ever will be held in Vienna (Austria, Europe) on April 30 - May 2, 2004
Visit the official www page
How something so blatently stupid is modded insightful I can't imagine. Seriously, openbsd has had only 1 remote hole in 7 entire years with its defaults. This is a factual public record of how good their defaults are, and you think that's not as good as net? Get real.