Slashdot Mirror
Busy BSD: New FreeBSD Status Report
edhall cut-and-pastes "After a six-month hiatus, a new
FreeBSD
Status Report has just been issued,
along with a promise to resume its bi-monthly publication.
As the report itself makes obvious, a lot has happened
over the last six months. Progress has been happening along many fronts; those groups making reports include: [snip] These are, of course, just the projects that remembered
to send in a report -- there are many more ongoing efforts
than listed here; see this
page for a fuller but not necessarily complete list
(you'll note that there are status reports for projects not listed there, such as the AMD64 port)."
About two weeks ago I decided to try and install Linux on my old K6-2 450mhz machine gathering dust in the basement.
A friend of mine gave me a few cd's that had something called 'Mandrake' on it.
He said "This is supposed to be the most user-friendly 'distro' out there. Give it a try."
So with trepidation about wiping out my beloved win98se install on the old machine, I jumped right in.
On firing up the install disk, the Man-drake installer asked me if I wanted to remove the win98se partition that already existed. After pondering this for several minutes I though, 'what the hell, I can always reinstall it!' So I let it fly.
After what seemed like 45 minutes of swapping cd's in-and-out of the drive, the man-drake (isn't that some sort of bird?) installer ask me what I wanted to use this linux machine for. So many choices! games, office, mail server, web server, about 2 dozen choices flooded my screen. This is madness! So after carefully considerating my options
I decided to choose them all! I would be a Linux power-user to end all linux power-users!
So after this decision was made I waited. And waited. And waited. During this I started to wonder. My Windows XP Home intallation on my other Peecee didn't ask me thse kind of questions, and it easily has the all the abilities that man-drake advertised to have. After all, I paid for WinXP Home. Sigh, I guess this it the price one pays
for being part of the linux elite.
Approximately 50 mintues later I get another prompt from the man-drake installer asking me what kind of GUI I wanted to use, KDE or GNOME. Fool me once, shame on you, fool me twice shame on me! I selected both and let it fly.
After only about 20 mintues this time it appeared the install was completed. The mandrake installer told me it was going to reboot and then I would revel in Linux goodness. I waited with baited breath while the reboot churned away, eagerly waiting the opportuntity to use the KDE/GNOME interface. Page after page of command line
stuff flew by my screen, seeming to get faster and faster as the time of my linux deliverance approached. Then, the screen flashed black (kinda like those scenes from the movie Wargames). I gasped and was presented with something like this:
bsh: blah/blah/blah/ ____
What the hell was this? Wasn't this man-drake linux supposed to be user friendly? Instead of the friendly confines of a WinXP like GUI instead I was given an ugly DOS like prompt, which looked supiciously like the TRS-80 system I first learned BASIC on in high school. Is this all the farther the great open-source movement has progressed?
After serveral minutes of sobbing and knashing of teeth, I came to a decision. All the linux fags out there were not going to defeat me! They were not going to cry "Bend over WinXP boy, you're going to take linux OUR WAY and like it!".
I quickly found my old musty copy of 'Unix in a Nutshell' from my college days and got to work. In a few hours I found out how to start the KDE GUI. This made life so much easier. After several days I was able to get the machine's 14.4 internal modem working with man-drake and connected to the internet, using a browser called Mozilla. Where oh where were the glorious pop-ups that appeared as I was surfing porn sites? Those bastards!
After several more days I was starting to feel somewhat comfortable. Using something called Gimp to manipulate my growing collection of adult images was becoming a habit. And because I was ashamed to let my friends and neighbors know I was using a gasp! free operating system like mandrake, I kept the pee-cee in the basement. Now my girlfriend things the sounds emanating from below are me just woodworking or lifting weights. I guess linux has freed me after all!
CMDRTACO CHECK YOUR EMAIL!
The End of FreeBSD
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's when you get distracte
Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureacratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.