Slashdot Mirror
FreeBSD to Celebrate 10 Year Anniversary in SF, CA
Dan writes "A long time ago, in a galaxy far far away...in the early part of 1993...the last 3 coordinators of the 'Unofficial 386BSD Patchkit' would go on to start the FreeBSD project that has grown to be used by millions of websites and installations around the world. Murray Stokely is talking about Jordan Hubbard, Nate Williams, and Rod Grimes. Looking for a catchy name, David Greenman suggested FreeBSD and it stuck. With the help of Walnut Creek CDROM, the first CDROM distribution, FreeBSD 1.0, was released in December of 1993."
BSD is dead man. Time to switch to Linux.
-----
One is born into aristocracy, but mediocrity can only be achieved through hard work.
Any netcraft surveys on the spread of BSd available?
What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0
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 bureaucratic 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.
Will this party be held in a San Francisco bath house? Will the Slashdot gang be there so I can fuck their buttholes?
Oct. 23 -- BSD resumed receiving life-sustaining care yesterday in a Florida hospital room, but many experts said there is virtually no hope that it will ever recover, despite it fan boy's desperate hopes.
"IF IT'S over a year, BSD's not ever going to get up," said Fred Plum, a professor emeritus at Weill Cornell College in New York. "You'd just don't see it. It just doesn't happen."
BSD, 39, has been in a persistent vegetative state since its heart stopped for unknown reasons in 1990. A feeding tube in BSD's stomach was removed this past Wednesday after its husband, Theo De Ratt, who said his wife had told him she (BSD) would not want to be kept alive under such circumstances, won a long series of court battles to have life-sustaining nourishment withdrawn so she (BSD) could die.
Cast:
Mr. Praline: John Cleese
Shop Owner: Michael Palin
A customer enters an operating system shop.
Mr. Praline: 'Ello, I wish to register a complaint. (The owner does not respond.)
Mr. Praline: 'Ello, Miss?
Owner: What do you mean "miss"?
Mr. Praline: I'm sorry, I have a cold. I wish to make a complaint!
Owner: We're closin' for lunch.
Mr. Praline: Never mind that, my lad. I wish to complain about this operating system what I purchased not half an hour ago from this very boutique.
Owner: Oh yes, the, uh, *BSD...What's,uh...What's wrong with it?
Mr. Praline: I'll tell you what's wrong with it, my lad. It's dead, that's what's wrong with it!
Owner: No, no, it's uh,...it's resting.
Mr. Praline: Look, matey, I know a dead operating system when I see one, and I'm looking at one right now.
Owner: No no it's not dead, it's, it's restin'! Remarkable OS, *BSD, idn'it, ay? Beautiful kernel!
Mr. Praline: The kernel don't enter into it. It's stone dead.
Owner: Nononono, no, no! It's resting!
Mr. Praline: All right then, if it's restin', I'll wake it up! (bashes at the keyboard) 'Ello, Mister *BSD! I've got a lovely fresh kernel update for you if you show...
(owner hits the keys)
Owner: There, it spewed some debug output to the command line!
Mr. Praline: No, it didn't, that was you hitting the keys!
Owner: I never!!
Mr. Praline: Yes, you did!
Owner: I never, never did anything...
Mr. Praline: (yelling and typing into the console repeatedly) 'ELLO COMMAND PROMPT!!!!! Testing! Testing! Testing! Testing! This is your nine o'clock cron job!
(Rips out hard drive from computer case and thumps it on the counter. Shoves it back inside the case and reboots the system - blank screen.)
Mr. Praline: Now that's what I call a dead operating system.
Owner: No, no.....No, it's stunned!
Mr. Praline: STUNNED?!?
Owner: Yeah! You stunned it, just as it was finishing an I/O task! *BSD stuns easily, major.
Mr. Praline: Um...now look...now look, mate, I've definitely 'ad enough of this. That operating system is definitely deceased, and when I purchased it not 'alf an hour ago, you assured me that its total lack of responsiveness was due to it bein' in the process of recompiling itself after a particularly comprehensive code update.
Owner: Well, it's...it's, ah...probably pining for some dilettante dabbling.
Mr. Praline: PININ' for some DILETTANTE DABBLING?!?!?!? What kind of talk is that? Look, why did it fall flat on its back the moment I started Emacs?
Owner: *BSD prefers swapping everything out to the hard drive! Remarkable variant, id'nit, squire? Lovely kernel!
Mr. Praline: Look, I took the liberty of examining the system when I got it home, and I discovered the only reason that it had been printing any text at all to the screen was because of all the WORRYING COMPILER WARNINGS encountered while it was being rebuilt.
(pause)
Owner: Well, o'course it was spitting out those warnings! If I hadn't updated the kernel with an unstable development build, you might have had your FTP server compromised [slashdot.org], and VOOM! Bye bye to your business.
Mr. Praline: "Server"?!? Mate, this OS wouldn't "serve" if you put four million volts through it! It's bleedin' demised!
Owner: No no! It's pining!
Mr. Praline: It's not pinin'! It's passed on! This OS is no more! It has ceased to be! It's expired and gone to meet its maker! [lemis.com] It's a stiff! Bereft of life, it rests in peace! It's kicked the bucket, it's shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisibile!! The numbers continue to decline for *BSD but FreeBSD may be hurting
To sign out or select 'Anonymous Coward' this time with your BSD rantings?
For a snicker, from saden1's description: 23, good looking, smart and sexy. I'm a geek without all the emotional and ideological baggage.
I think it's time that the slashdot staff has to take action against those lame BSD posts... Every single news fact about BSD gets these empty headed posts.
Check my site: http://pixel.pagina.nl
It's not pinin'. It's passed on. This OS is no more. It has ceased to be. It's expired and gone to meet its maker. It's a stiff. Bereft of life, it rests in peace. It's kicked the bucket, it's shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisibile. *BSD is an ex-operating system.
Much as I love the clean layout and careful design of FreeBSD (and in fairness the other BSD flavours), it's a lot of hassle to maintain. When a security patch appears, needing the full development toolchain, kernel and system source and time to patch and rebuild and install is tiresome. On my Debian boxes, it's one simple command.
So is any form of binary patching planned for future FreeBSD releases? I'd love this, and I'd move my Debian boxes over to FreeBSD immediately.
All the *BSD is dying posts are contained in this one post. If you have mod points, please mod this up so that everybody will know that *BSD is dying! No need to post your own, as it will only be redundant!
Oh, and if I've missed any, please add your troll as a reply and I'll include it in the next Troll-in-one.
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
The *BSD Wailing Song
What's left for me to see
In my ship I sailed so far
What can the answer be
Don't know what the questions are.
And after all I've done
Still I cannot feel the sun
Tell me save me
In the end our lost souls must repent.
I must know it is for certain
Can it be the final curtain
As long as the wind will blow
I'll be searching high and low.
Who knows what's really true
They say the end is so near
Why are we all so cruel
We just fill ourselves with fear.
And heaven and hell will turn
All that we love shall burn
Hear me trust me
In the end our lost sould must repent.
I must know it is for certain
Can it be the final curtain
As long as the wind will blow
I'll be searching high and low
Final curtain
Final curtain
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
pressed to bsd lips
bsd drink up
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.
BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
It is common knowledge that *BSD is dying. Almost everyone knows that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The erosion of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell a
The Failure of *BSD
Of course we can all agree that BSD is a failure, but why did BSD fail Once you get past the fact that BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know BSD keeps losing market share but why Is it the problematic personalities of many of the key players Or is it larger than their troubled personalities
The record is clear on one thing no operating system has ever come back from the grave. Efforts to resuscitate BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for BSD.
Actually, only 8 or 9 years later, since I haven't seen Rod in the last year or two. He's a bitter, angry asshole who's ruined more than a couple business deals with various people I've known. I don't think I've ever met anyone who actually /liked/ Rod. He was trying to run a business as a systems integrator in Gresham, Oregon and that failed miserably. He ran a spam operation for a good while, putting all that BSD knowledge to "good" use. Yes, BSD is dying, rightfully so.
[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. I
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major marketing surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.
Fact: FreeBSD is dying
BSD IS DEAD
"Do not stand at my hard disk and forever weep.
I am not there; I do not sleep.
I am a thousand winds that blow.
I am the diamond glints on snow.
I am the sunlight on ripened grain.
I am the gentle autumn's rain.
When you reboot in the morning's hush
I am the swift uplifting rush
Of quiet birds in circled flight.
I am the soft stars that shine at night.
Do not stand at my hard disk and forever cry.
I am not there. "
BSD IS DEAD
fucking BSD alive not is
Now make a sentence out of that...
Dupe! This is already in the troll-in-one, asswipe!
The person posting the Troll-in-one is a BSD user trying trying to encourage people not to post the truth about BSD.
Feel free to post the truth as often as nessecary until everyone understands, folks.
So who else has contributed broken software to a 1.0 release?
I'm the reason why the mitsumi CD-ROM driver was broken, and of course Rod had just cut the gold master (and back then it was a major pain to make masters) and could not update the sources.
After about 20 patches, he just just gave me a commit bit...:)
BWP
You totally missed the point. Linux vendors contribute a LOT more code to project such as XFree86 than any of you BSD fanboy's.
If you don't believe me, check out NERO's Last Measure of the Internet
haha pwnd
[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. I
All major marketing surveys show that FreeBSD has steadily declined in market share. FreeBSD is very sick and its long term survival prospects are very dim.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.
In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking.
Fact: FreeBSD is dying
YHBT. YHL. HAND.
All our times have come
Here but now they're gone
Mac OS don't fear the reaper
Nor do the windows, SUN or the rain..we can be like they are
Come on baby...don't fear the reaper
Baby take my hand...don't fear the reaper
We'll be able to fly...don't fear the reaper
BSD's bought the farm....
Distro is done
Here but now they're gone
Romeo and Juliet
Are together in eternity...Romeo and Juliet
40,000 server crashes every day...Like Romeo and Juliet
40,000 workstations reformatted everyday...Redefine happiness
Another 40,000 coming everyday...We can be like they are
Come on baby...don't fear the reaper
Baby take my hand...don't fear the reaper
We'll be able to fly...don't fear the reaper
BSD's bought the farm...
Love of two is one
Here but now they're gone
Came the last night of sadness
And it was clear she couldn't log on
Then the file was opened the wind appeared
The mobo blew then disappeared
The curtains flew then Jordan Hubbard and Michael Smith appeared...saying don't be afraid
Come on baby...and she had no fear
And she ran to them...then they started to fly
They looked backward and said goodbye...she had become like they are
She had taken their hand...she had become like they are
Come on baby...don't fear the reaper "
if this is offtopic, why isn't the parent of this post not?
Boo hoo hoo. Sob.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
1. You can play many great games on it.
2. It can easily be used by my grandma.
3. It has many excellent GUIs you can choose from.
4. There is much support available for it.
5. It is a single, coherent, all-in-one OS.
6. It can be run on many platforms, including x86.
7. You need not compile anything or know C.
8. Support for the latest hardware is generally quite good.
9. It is compatible with GNU/Linux and even includes a Linux emulation layer.
10.It is one of the most alive operating systems in existence, with improvements being made to it almost daily.
It doesn't even contain a link to the news flash
Oh god that cracked me up. I had to have a secondlook at it to realise that it was a troll of a troll.
Good work. Nice to know that someone out there isn't taking the trolls seriously.
I wonder what gift Sco will be giving the BSD team... Maybe they'll donate some code enabling FreeBSD to finally be "ready for the enterprise." That or maybe they can license "Happy Birthday" for us so we can all sing it at the party! I for one can't wait to see more wild antics of Darl the Clown! WoooHooo Birtday!!!!!
"To lead the people, you must walk behind them"
Or "Grimy", as he liked to be called.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral. In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking. It's a fact: FreeBSD is dying.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The erosion of user base for FreeBSD continues in a head spinning downward spiral. In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking. It's a fact: FreeBSD is dying.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.