Slashdot Mirror
FreeBSD 5.0 Developer Preview #1 Released
An Anonymous Coward writes: "The FreeBSD developers just announced the release of an official snapshot of the upcoming FreeBSD 5.0 which should be expected in November. Time to try out amazing new feature like background fsck, FFS snapshots, KSC, devfs, SMPng and many more. Check the Release Notes for detailed information." Read on for a list of ISO mirrors, too.
Thanks to AEtherSPOON, you can spare the main servers and use one of these FTP mirrors to grab the ISO:
Sounds interesting, but fsck isn't something you should run in the background. I mean, do you really want to be writing to the disk at the same time you're checking for errors? Maybe it's just my parinoia. If the developers pull this off safely and with no or barely any noticable slowdown, my hat is off to them.
I'm a repairman in an imperfect world.
As far as I know of... there isn't any noticeable tension between OpenBSD and FreeBSD... but of course, I don't pay attention to the politics; I just use what is best for each situation.
Well, at any time you want you can download a snapshot of Slackware's current tree, which is the development happening in realtime... probably can't get any faster beta releases then that ;)
the story told to my OS class was that Theo for whatever reason split from either Free or NetBSD to OpenBSD. For a while, the two were pretty much the same. Then someone r00t3d Theo's machine. Thus OpenBSD took on the task of being the most secure OS out there, and I think they've done a pretty good job, particularly in their development practices that encourage finding bugs and getting things right the first time.
The One Rule Of Chess You'll Ever Need: Don't play someone who carries a kit in their bookbag.
Right, it wasn't Tara, but IPF. OpenBSD didn't end up killing Tara...er, IPF, but disowning it. But that was mostly IPFs fault. So then IPFs twin sister PF showed up claiming to be the rightful heiress to the OpenBSD fortunes, and now IPF is forced to hang around the FreeBSD family much more then ever, which is making their local firewall jealous.
Then in a big suprise, IPF comes back from her romping aroung NetBSD, FreeBSD and the red-light district of commercial Unix to deliver a bastard child... er, fork, of OpenBSD 3.0, and the Twin Suns of OpenBSD are silently duking it out through their invisible firewalls with divergent syntax. FreeBSD slips SMP into NetBSDs drink, and then, stay tuned for next weeks episode of "As Make World Tunes"...
I think this post clearly indicates that it is my bedtime. Theo vs. NetBSD's remainder is old dead news. IPF wasn't as "Free (libre)" as the BSD community had assumed, and when Mr. IPF held this over Theo deGUUYs's head, deGUUY had a schitzoid reaction and hacked it out of OBSD. The remainder of the BSD community has more important things to worry about, OBSD embraced and extended a Free IPF alternative in time for the 3.0 release, and again OpenBSD has taken the high road.
Theo is an unfairly maligned jerk who maintains a Free OS with uncompromizing values, where NetBSD and FreeBSD don't mind "bending the(ir) rules" now and then. He is most definitely not a software visionary, who rather believes that a 30 year old security model is the best choice for today's global internetwork of secure systems - because that way there are no surprises. The FreeBSD guys are hardworking arbitrary freeware oligarcho-capitalist volunteers just trying to keep thier releases regular.
Darren Reed helped OpenBSD become what it is today, just as Theo de Raadt helped NetBSD become what it was, but both groups parted ways. IPF feels like a second class citizen without OpenBSD, so Mr Reed forked his own openbsd30.ipfilter.org, but IPF plays nice with most Unices. PF is now the OBSD Chosen One. Soap Operas should be criminalized. Support FreeBSD; but pay for OpenBSD, for when the shit hits the fan. Better safe than sorry, better secure than friendly. Computers don't need hugs. Oh, and Soap Operas need to be outlawed. Not to mention criminalized. Save Tara - she's a hottie.