Slashdot Mirror
Chock Full o' NetBSD!
jschauma writes "While it's no Indigo
Espresso or a VAX Bar (though,
of course, there is NetBSD/sgimips and NetBSD/vax), at least you can log
in on a Mr.
Coffee. And while the JavaStation has been running NetBSD for a while,
full support is now completely in-tree:
NetBSD's Martin Husemann announced today
that he has fixed all outstanding issues with JavaStation support. This
means, that you can now run your JavaStation with a stock distribution of NetBSD/sparc. The JavaStation-NC
is a network computer class machine built on the microSPARC-IIep processor.
More information about the JavaStation can be found in the JavaStation
HOWTO, Martin's email to
the port-sparc mailing list and Valeriy E. Ushakov's paper 'Porting NetBSD to
JavaStation-NC.'"
_d8b____________________d8b_______d8,
_?88____________________88P______`8P
__88b__________________d88
__888888b__.d888b,_d888888________88b_.d888b,
__88P_`?8b_?8b,___d8P'_?88________88P_?8b,
_d88,__d88___`?8b_88b__,88b______d88____`?8b
d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'
______d8b________________________d8b
______88P________________________88P
_____d88________________________d88
_d888888___d8888b_d888b8b___d888888
d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
88b__,88b_88b____88b__,88b_88b__,88b
`?88P'`88b`?888P'`?88P'`88b`?88P'`88b
For any wanna-be trolls:
*BSD is not dying and you are not cute,funny, or clever. Get over it.
Elegy For *BSD
I am a *BSD user
and I try hard to be brave
That is a tall order,
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
I'm sure the 12 people that use NetBSD & Sparc are gonna be super happy!
DEAL
1. You can not play games on it.
2. It cannot be used by my grandma.
3. It lacks a GUI of any note.
4. There is no support available for it.
5. It is an assortment of fragmented OSes.
6. It cannot be run on the x86 platform.
7. You have to compile everything and know C.
8. Support for the latest hardware is always poor.
9. It is incompatiable with GNU/Linux.
10. It is dying.
[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
Area horse owners, especially those around Echo Lake, may want to keep a close eye on their equine companions after two recent instances of abuse and theft.
A naked man was found having intercourse with a horse in a stable on McCaffery Road around 6:30 a.m. on Nov. 17. Flathead County Sheriff Jim Dupont said the man, still nude, fled on foot when the owner of the horse entered the stable.
"He left his boots and a bottle of hand lotion behind," Dupont said.
Also found were a Yoda doll, Crisco, and a ticket marked "FreeBSD anniversary party". Sheriff's deputies concur that the suspect is an unemployed BSD developer.
The incident came just days after a Flathead County deputy reported his horse missing. The horse had apparently been taken from its stable near Echo Lake early in the weekend. The horse was back in its stable by late in the weekend with traces of lanolin around its rectum, Dupont said.
"It appears we have a serial horse rapist," Dupont said. The sheriff's office is investigating, and Dupont advised horse owners to be vigilant. "BSD is dying, and there is nothing which these BSD weirdos won't do in an act of desperation," he concluded.
EMERGE!
(this was the obligatory Gentoo plug)
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD 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 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 OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dead
I love BSD. It's so easy for any Evil Corporation to take it, modify it, redistribute it under a draconian closed-source license, charge an arm-and-a-leg for it, and REAP THE REWARDS! Even if 99% of the code is untouched. Muahahaha!
Guys, wake up. BSD is not free software. It never was. Well it is free, but it's not designed to stay free due to its overly permissive license. Any true supporter of free software would shun it and stick with GNU/Linux these days.
BSD comes with a lot of GNU utils. Heck, BSD wouldn't exist without GNU gcc. They *owe* the GNU project, and would do well to switch their license to the FSF's GPL.
(Let me make a piece of software. Call it RedWM, the Red Window Manager, and within it offer only shades of burgundy and not any real Red. That's an analogy for how misnamed NetBSD truly is!)
*BSD is like a problem child dying of some rare incurable disease.
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.
You've illegally invaded a sovereign nation. That hardly makes you one of the "good guys", asshat.
The ends never justifies the means.
You nigger-loving cocksuckers are next!
Bring it on...
[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
Here.
and here.
(Stupid lameness filter
must type something here
to get enough characters per line).
the last link is booby trapped with some kind of weird thing.
Sixty years ago, I worked in what was once my Grandfather's Greenhouses. Gramps had died a year earlier and Grandma, now in her seventies had been forced to sell to the competition. I got a job with the new owners and mostly worked the range by myself. That summer, they hired a man to help me get the benches ready for the fall planting.
Ike always looked like he was three days from a shave and his whiskers were dirty white, shaded by the brim of his battered felt fedora.
He did not chew tobacco but the corners of his mouth turned down in a way that, at any moment, I expected a trickle of thin, brown juice to creep down his chin. His bushy, brown eyebrows shaded pale, gray eyes.
The old-timer extended his hand, lifted his leg like a dog about to mark a bush and let go the loudest fart I ever heard. The old fellow then winked at me, "Ike Thomas is the name and playing pecker's my game."
I thought he said, "Checkers." I was nineteen, green as grass. I said, "I was never much good at that game."
"Now me," said Ike, "I just love jumping men . . ."
"I'll bet you do."
". . . and grabbing on to their peckers," said Ike.
"I though we were talking about . . ."
"You like jumping old men's peckers?"
I shook my head.
"I reckon we'll have to remedy that." Ike lifted his right leg and let go another tremendous fart. "He said, "We best be getting to work."
That summer of 1941 was a more innocent time. I learned most of the sex I knew from those little eight pager cartoon booklets of comic-page characters going at it. Young men read them in the privacy of an outside john, played with themselves, by themselves and didn't brag about it. Sometimes, we got off with a trusted friend and helped each other out.
Under the greenhouse glass, the temperature sometimes climbed over the hundred degree mark. I had worked stripped to the waist since April and was as brown as a berry. On only his second day on the job and in the middle of August, Ike wore old fashioned overalls. Those and socks in his high-top work shoes was every stitch he wore. When he bent forward, the bib front billowed out and I could see the white curly hairs on his chest and belly.
"Me? I just love to eat pussy!" Ike licked his lips from corner to corner then sticking his tongue out far enough that the tip could touch the end of his nose. He said, A man's not a man till he knows first hand, the flavor of a lady's pussy."
"People do that?"
He winked. "Of course the taste of a hard cock ain't to be sneezed at neither. Now you answer me, yes or no. Does a man's cock taste salty or not?"
"I never . . ."
"Well, old Ike's willing to let you find out."
"No way."
"Just teasing," said Ike. "But don't give me no sass or I'll show you my ass." He winked. "Might show it to you anyway, if you was to ask."
"Why would I do that?"
"Curiosity, maybe. I'm guessing you never had a good piece of man ass."
"I'm no queer."
"Now don't be getting judgmental. Enjoying what's at hand ain't being queer. It's taking pleasure where you find it with anybody willing." Ike slipped a hand into the side slit of his overalls and I could tell he was fondling and straightening out his cock. "Now I admit I got me a hole that satisfied a few guys."
I swallowed, hard.
Ike winked. "Care to be asshole buddies?"
***
We worked steadily until noon. Ike drew a worn pocket watch from the bib pocket of his loose overalls and croaked, "Bean time. But first its time to reel out our limber hoses and make with the golden arches before lunch."
I followed Ike to the end of the greenhouse where he stopped at the outside wall of the potting shed. He opened his fly, fished inside, and finger-hooked a soft white penis with a pouting foreskin puckered half an inch past the hidden head.
bush is a great president!
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.
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.
Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
Joseph Mallett, an ex-committer.
10814Are you UNCIRCUMCISED?
Then you should FEEL dirty and ASHAMED! How can you have that aardvark hanging between your filthy puke inducing crotch when there is a treatment for the UGLY DICK condition? That's right, as a Linux chick I can't count the many times I've encountered this DIGUSTING problem.
Linux Guys are VERY GROSSLY uncircumcised do to the fact that the leaders of this movement are not. Linus "long foreskin" Torvalds and Alan "uncut" Cox are PRIME examples of ugly SMELLY SMEGMA dick. I suggest that we take up a collection and CIRCUMCISE these guys.
Until this is done, I'll only use GPL software from properly circumcised and beautiful cocked men like RMS. So NO Linux kernel for this HOT GPL chick..only the HURD until these filthy uncircumcised Linux guys get the operation and become clean.
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.
What We Can Learn From NetBSD
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.
Rolf!!ROLF!!!
l!ol!ol!ol!ol!LO!LO!LO!LO!LOLOLO!OL
BSD is in my pants!!.
get out!! looooooooooool
I know it is now almost a mantra set in stone that "NetBSD is dying". Unfortunately, the abuse of that fact by trolls has obscured the truth, that truth being that NetBSD really is dying.
My main reason for moving away from NetBSD has been twofold. First, to avoid the constant political infighting and bickering. And secondly, to investigate more promising and viable entries into the operating systems sweepstakes. NetBSD is no longer a legitimate player, I'm sorry to say.
Make sure to ask what BSD stands for - is it Butt Sex Department or Boiz Sucking Dick?
Many people, even Linux users, feel the GPL is a bad license because of it's viral nature. Not just a bad license for big business, but for open source developers too. It removes the freedom we all want; choice.
Debian doesn't support nearly as many platforms as NetBSD. Debian doesn't offer the cross-platform tools NetBSD. Debian also doesn't offer binary emulation support like NetBSD does.
I'm trolling a troll who's trolling a troll. Nice.
You're a big boy now. High time you started acting like one.
What does "BSD" stand for - is it Butt Sex Department or Boiz Sucking Dick?
Elegy For *BSD
I am a *BSD user
and I try hard to be brave
That is a tall order
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
Bones: It's dead, Jim.
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.
NetBSD is dying.
Really, this makes no sense at all. NetBSD has justifiably gained the reputation as the graveyard OS. It reeks of death coming and going.
... and sleeps with the fishes.
Somewhere, in a lonely hospital room,
Somewhere, in a lonely hospital room,
*BSD is dying
huh?
Shut up, nigger.
Never let your emotions get mixed up with something as silly as a computer
operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
Hope this helps.
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.
Check out the facts: *BSD is dead
The Year of Our Lord 2003 has been a particularly bad year for the "B"s,
- Bob Hope
- Buddy Ebsen
- Buddy Hackett
- Barry White
- BSD
This honored list of dead is but a small token of adieu from the many fans of the deceased.These dead were truly some American Icons. They will be missed.
Subject says it all. End of story.
In a startling turn of events today, a previously little-known fact came into the public eye: "*BSD Sux0rs". This came as a complete surprise to the BUWLA, or BSD Users With Large Assholes, as they previously thought that *BSD 0wned.
"You see, even though I have never contributed code to any BSD project, I thought it was my duty to be a big asshole to others which don't use the OS I do, because it just 0wnz.", said one FreeBSD user. "Now that I know it sux0rs, though, I have to go find something else to be an asshole about."
One notorious OpenBSD fanatic known as WideOpen, told reporters, "I have to kill myself. This isn't how it was supposed to happen. My BSD has always been the best, and shouting that opinion in other people's faces at every chance I got has been my only hobby. It was all I ever did. It was what got me out of bed in the morning. Now I have to die. I will jam my bedpost up my ass until I hit my brain. It is the only way to go: BSD style."
In the volatile world of operating systems anything can happen. "At least we don't sux0r as much as Windows users", BigAzz, a relatively well-known NetBSD user said. "Screaming things in people's faces is my calling. Now I need to scream that BSD sux0rs. What a sad world. At least I won't kill myself like those uber-asshole OpenBSD guys. They are just way over the top. Or were, at least."
Nobody knows for sure what the future holds for the state of operating systems, but with Netcraft confirming the sux0r status, *BSD users all over the world will have to stick something else up their asses from now on or risk looking even more gay than they used to.
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.
In the final analysis, *BSD is dying.
Somewhere, in a lonely hospital room,
*BSD is dying.
_d8b____________________d8b_______d8,
_?88____________________88P______`8P
__88b__________________d88
__888888b__.d888b,_d888888________88b_.d888b,
__88P_`?8b_?8b,___d8P'_?88________88P_?8b,
_d88,__d88___`?8b_88b__,88b______d88____`?8b
d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'
______d8b________________________d8b
______88P________________________88P
_____d88________________________d88
_d888888___d8888b_d888b8b___d888888
d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
88b__,88b_88b____88b__,88b_88b__,88b
`?88P'`88b`?888P'`?88P'`88b`?88P'`88b
"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. "
Thought you'd be interested in this little tidbit:
Hope this helps!
- Dave
BSD you grow in the ghetto, living second rate
And your eyes will sing a song of deep hate.
The places you play and where you stay
Looks like one great big alley way.
You'll admire all the numberbook takers,
Thugs, BSD pimps and pushers, and the big money makers.
You are dead *BSD.
You have departed this mortal world.
You are no more.
You are dead *BSd
So very dead.
This troll supported by the letters R, I and P.