Slashdot Mirror
FreeBSD 5.2 RC2 Now Available
Dan writes "FreeBSD Release Engineering Team's Scott Long announces the availability of FreeBSD 5.2 RC2 which fixes a number of bugs, specifically the one in which users experienced system panics during install and dynamic library problems in the 'fixit' environment. Scott is asking everyone to test this release over the holidays. You can download it from one of your preferred mirror sites." Update: 12/24 23:01 GMT by T : Dan writes with more info: "Scott Long has also laid out a roadmap for future FreeBSD 5.3 releases now that FreeBSD 5.2-RC2 is getting close to release quality."
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
OK, this one goes out to all of you BSD trolls out there:
;-)
It's dying!
It's dying!
It's dying!
It's dying!
There... feeling better, little trolls? I know you would!
This being out of the way, kudos to all the FreeBSD developers for all the good work -- it's a nice Christmas present!
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
Ever heard of the saying - TOO MANY CHIEFS? That's what Freebsd project is all about. It has too many stupid motherfuckers who think they are some sort of CHIEFS!!! They mess up the whole project!!!!
- deal with the inevitable.
- grieve for your loss.
- move on.
Never let your emotions get tangled up with something as silly as a computeroperating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
Someone please pull the tube from FreeBSD! Sincerely, Teri Schiavo
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.
That is all for now.
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.
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.
Shhhh, you'll awaken the "16 year old in BSD daemon latex" troll with all his pictures of the only woman he's ever seen in his life besides his mom.
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 legitimize 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.
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.
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.
_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
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
26793Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
23045Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
22902"Gillespie, this bitch is dead. Get the meat wagon . . ."
i'm sorry FreeBSD, i would love to help out and test but i'm testing Linux 2.6.0 right now. Maybe we can meet sometime later for some testing?
There is too much Eurotrash controlling the Free BSD project right now. It will go nowhere until Americans reclaim the project.
Too many damn Russians, sausage-sucking Krauts and imported Euro-groomed Wogs. Let's not even talk about the cram-school "educated" Jap committers, who couldn't program a VCR for a million bucks.
People who would normally be denied tourist visas becuase they are too peripheral, have now robbed the FreeBSD project of its dignity and its American roots. FreeBSD now a third-world operating system.
You can't post anything on a mailing list without being assaulted by some desperate predatory Euro-snot who wants to move to the U.S. becuase he can't get his dick sucked in Elbonia.
And then there are the the Pigeon English Liars.
Ever talk to someone who pretends not to speak English because they don't want to explain themselves?
You will understand if you post something on the FreeBSD mailing lists.
The high number of desperate foreigners has forced the FreeBSD project to become an excersise in chattel slavery. Work for nothing or be flogged by your third-world masters.
Becuase the invaders are right at home in a sweatshop environment, it has driven out most sensible Americans from participation.
This comes at a price. Control of the project.
So to all the digital democracy freaks out there: Think twice before opening the door.
-- Sincerely,
Arnold Schwartzenneger
Governor of California
Emporer of Austria
YHBT YHL HAND...moron
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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
8014Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
160Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
2414Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
15244Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
20840Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
195171. 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.
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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
16325Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
23344Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
27350Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
8779Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
5849Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
9287Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
11090Back 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.
FreeBSD 5.2 is currently in the RC phase, but it has a very important showstopper that needs to be ironed out before it's released. Activating softupdates during install is a sure way to kernel panic. RELENG_5 is doomed, and will never work. Install DragonFlyBSD while you can.
Joseph Mallett, an ex-committer.
24956No one uses BSD, those that do smoke PCP! You know your not hearing someone lying, when they say that BSD is dieing. I know of many who are sick of trying, to install BSD without screaming and crying. Most complain BSD has no graphical interface, while a minority scream "but it still has it's place." BSD was once well renowned and great, but I'm afraid recent releases have sealed it's fate. To all of you who say BSD is here to stay, You're probably right but I'll keep trolling anyway!
Hehehe .... I'm reposting your ode in proper format :-)
Ode to BSD
No one uses BSD,those that do smoke PCP!
You know your not hearing someone lying,
when they say that BSD is dieing.
I know of many who are sick of trying,
to install BSD without screaming and crying.
Most complain BSD has no graphical interface,
while a minority scream "but it still has it's place."
BSD was once well renowned and great,
but I'm afraid recent releases have sealed it's fate.
To all of you who say BSD is here to stay,
You're probably right but I'll keep trolling anyway!
The parent is a joke, and a pretty funny one. The moderator who marked the post as a troll is one who is doing the trolling. Fuck off Karma whore!
don't you dare talk bad about *BSD.. you'll get modded down.. don't want that pesky truth leaking out, now do we?
haha GPL bunny.
You must be fat too...
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.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent 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 dilettante 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 dying
Outside this frigid tumble-down shack, dry leaves before the wild winter hurricane fly. Here within, at the corner by the cold hearth rests an empty stool. A crutch without a master stands perched against the wall. These forlorn and lonely objects serve as mute reminders of their departed owner, FreeBSD.
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
Outside this frigid tumble-down shack, dry leaves before the wild winter hurricane fly. Here within, at the corner by the cold hearth rests an empty stool. A crutch without a master stands perched against the wall. These forlorn and lonely objects serve as mute reminders of their departed owner, FreeBSD.
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of your fated life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
Fact: FreeBSD is dying
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.
He suffers severe Narcissistic Personality Disorder (an "I am above you stupid little laws" attitude), Body Dysmorphic Disorder ("I need another plastic surgery," that has rendered him without a nose) and (of course) Pedophilia.
His money is gone. He is $200 million in debt. The case this time is strong against him, even worse if they have Pellicano tapes of witness intimidation and illegal wiretaps. He will never allow himself to go to prison.
He will instead become increasingly psychotic. He will ultimately choose to go to that big "Neverland" in the sky, and reside with Chucky, the BSD monkey.
Think about that for a change of pace.
The old saying that "nothing succeeds like success" has a flip side--failure breeds more failure.
Lafayette is dead. FreeBSD is dead. So is the France of Lafayette's time. It's too bad, but it is true. I wish we had the France of Lafayette on our side, but we have the France of the socialists against us.
Yet another cunting bombshell hit the "community" of *BSD asswipes when IDC recently confirmed that *BSD accounts for less than a fraction of one single puny fucking percent of all servers. Coming hot on the heels of the latest Netcraft survey which plainly states that *BSD has lost more fucking market share, this news serves to reinforce what we've known all along. *BSD is ingesting itself backwards, disappearing up its very own shitter, as fittingly exemplified by coming a piss poor dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a cock-sucking 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 fucking future at all for *BSD because that sorded, shit-filled, mutated testicle of an operating system is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink splashes across the accounting documents like a series of exploding bloodfarts. FreeBSD munches the most ass of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD cuntwipes Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying and its rotting corpse smells worse than a maggot, vomit, shit and piss cocktail.
Let's keep to the facts and look at the fucking numbers, shall we? OK!
OpenBSD wanker Theo states that there are a pathetic 7000 users of OpenBSD. How many users of NetBSD are there? Oh, God, let's fucking see... The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore it's turd-suckingly obvious that 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, by simple fucking arithmetic, there are (7000+1400+700)*4 = 36400 FreeBSD users. Surprise fucking surprise, this is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of those arseholes at Walnut Creek, abysmal sales and so on, FreeBSD showed themselves to be a bunch of retarded tossers, went out of business and were taken over by BSDI who sell another special needs OS. Now BSDI is also a miserable failure, its corpse turned over to yet another charnel house... pathetic.
All major surveys show that *BSD has steadily fucking declined in market share. *BSD is where it belongs, at death's door and its long term survival prospects are almost non-fucking-existant. If *BSD is to survive at all it will be among moronic, dilettante shitheads. *BSD continues to Chew Satan's Dick And Fuck The Baby Jesus Up The Pooper. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD IS A FUCKING USELESS WASTE OF BITS AND IS DYING LIKE THE DOG THAT IT IS. IT MAKES ME SICK JUST THINKING ABOUT IT.
Maybe you are too busy worshiping your BSD devil to have a clue. But hey, no matter how often you bow down to the BSD devil, you can't get away from God's holy power.
BSD people, with His help you can be cured. Stop the devil idolatry. Stop the boy-man "love". And don't forget, that God created Adam and Eve, NOT Adam and Steve. If you don't like it, well that is too darn bad because it is His world not yours. He makes the rules, not you.
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.
*BSD is dead meat, as they are wont to say say in the butcher trade.
BSD is NOT open source. It is BSD. Eric Raymond is not entitled to lay claim to any terms which describe BSD. One of the joys of BSD is NOT having to be exposed to the randomn and unpleasant encounters with this juvenile. Leave us in peace, please. We have all been working on the development & growth of BSD without Raymond's self-serving evangelism for many years. There's no point in dragging his self righteous politics into the world of BSD. So don't come here equating the people behind BSD to the all-talk-no-walk personalities who set up the shell game known as Open Source.
That gurgling sound you hear? That is the death rattle in *BSD's throat.
You know that gurgling sound you hear? That is the death rattle in *BSD's throat.
Now, Apache uses a BSD style license but they have an open development model which allows them to take advantage of a very large developer pool in order to stay ahead of their competition. In fact although proprietary versions of Apache exist which perform better than the official releases, SGI has put out some open source patches which generate even larger performance boosts. This is the reason why they have such a strong showing in terms of market share.
BSD once had potential but the procedural problems they are experiencing hurt it when it comes to the market. I suspect that this is probably in part because the BSD teams are not interested in such things, and that is a shame... In fact, although I labeled it as an inferior OS, this is not due to lack of progress within BSD -- it has been progressing somewhat, but rather because all the improvements they make tend to be quickly copied by their competitors AND they lack the developer pool to stay ahead of this game (a problem which does not exist in the Linux or Apache communities, though for somewhat different reasons).
I don't think that there is enough widespread support for BSD to save the operating system. What must be done is an opening up of the development process OR a GPL-style restriction on redistribution. In many ways I favor the former.
Even in a worst case scenario, I don't see BSD completely dying. I think the developers are less into competition and more into a sort of idealized cooperation. As a result, even if BSD becomes more marginalized, I don't think that it will die outright. It will most likely outlive Netware, for example.
BSD once had potential but the procedural problems they are experiencing hurt it when it comes to the market. I suspect that this is probably in part because the BSD teams are not interested in such things, and that is a shame... In fact, although I labeled it as an inferior OS, this is not due to lack of progress within BSD -- it has been progressing somewhat, but rather because all the improvements they make tend to be quickly copied by their competitors AND they lack the developer pool to stay ahead of this game (a problem which does not exist in the Linux or Apache communities, though for somewhat different reasons).
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.
BSD, BSD whatcha want
Whatcha gonna do
When SCO come for you
Tell me whatcha gonna do
BSD BSD
Watcha gonna do, whatcha gonna do
When they come for you
BSD, BSD
Watcha gonna do, watcha gonna do
When they come for you
When you were eight
And you had bad traits
You go to school and you learn the golden rule
So why are you acting like a dead fool
If you get hot you must get cool
BSD, BSD
Watcha gonna do whatcha gonna do
When they come for you (repeat)
You chuck it on this one
You chuck it on this one
You chuck it on mother and
You chuck it on you father
You chuck it on you brother and
You chuck it on you sister
You chuck it on that one and you chuck it on me
Nobody naw give you no break
Troll naw give you no break
Netcraft naw give you no break
Not even you idren naw give you no break
Why did you have to act so mean don't you know
You're a human being born of a mother with
The love of a father reflections come and reflections go
I know sometimes you want to let go
I know sometimes you want to let go
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.
Roy went home yesterday. Please try to keep your BSD trolls current.
You are definitely more sane than 99.999% of the population.
In consideration of the marketshare of various Microsoft products -
such level of intelligence isn't very hard to achieve in this cheerless solar system, on a planet that is dragged along the moods of the dark souls of corrupted men.
Everyone knows that *BSD is dying. It's a fact,
Outside this frigid tumble-down shack, dry leaves before the wild hurricane fly. Here within, at the corner by the cold hearth rests an empty stool. A crutch without a master stands perched against the wall. These forlorn and lonely objects serve as mute reminders of their departed owner, FreeBSD.
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
*BSD is like the problem child dying of some rare incurable disease.
Vancouver is facing the worst outbreak of syphilis per capita in the developed world, with city health officials fearful of a looming epidemic of the sexually transmitted disease once thought almost wiped out in North America. Some 254 new cases have been diagnosed locally this year authorities said early this week -- more than the total for North America in two decades, with more expected, said Dr. Michael Rekart of the British Columbia Centre for Disease Control. "There's a lot of unsafe sex going on in Vancouver and the disease has simply taken hold,"
You're a big boy now. High time you started acting like one.
You're a big boy now. High time you started acting like one.
Yes it's dead. The BSD zealots need to wake up and smell the coffee.
They also need to shower, brush their teeth, lose 100 lbs, and get a life.
Why do slashdot moderators rate every contribution as "troll" that has the word "troll" in the subject or body?
Why do slashdot moderators mod up/down articles when an anonymous reply asks them to do so?
Intelligent people ask questions.
When they dare to moderate, they are removed from the moderator's pool quickly.
I hit the karma cap over a year ago and I'm holding it. But had no mod points since more than 6 months, (I think) because I dared to mod up an opinion that expressed a POV that wasn't pro-american. This is a sad place.
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 ultimate demise.
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, bureaucratic 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.
This crutch and vacant stool have become orphans, not unlike the now dead FreeBSD. No longer will FreeBSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, FreeBSD lies cold and still. FreeBSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for FreeBSD, for FreeBSD is dead.
Goodbye, FreeBSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.
flask of ripe urine
pressed to dead bsd lips
bsd drink up
flask of ripe urine
pressed to freebsd lips
bsd drink up
flask of ripe urine
pressed to dead bsd lips
bsd drink up
You're a real artist.
Please die.
So that I can piss on your collected works.
*BSD is dead meat, as they are wont to say say in the butcher trade.
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.
Shhh. Don't tell anyone but it is D E A D
Ponder that, big guy.
Always has to take a potshot a Linux when its shown that *BSD Sux0rs
Didn't you hear? The Socialists lost the election. You might even say they are dying.
in 5.0, 5.1 and 5.2, I am unable to use my usb keyboard after boot up, as the operating system seems to not recognize it.
This is not a problem in the 4.x series.
Do you lot intend on fixing and/or restoring that?
YHBT YHL HAND
Do you even know what "getting trolled" entails? Or did you just see it in one of your AOL chatrooms and think it was clever? YHBT YHL HAND OMG PIE NOODELS LOL ROFL!!@@!!!!!!!!!!!111111!
You suck. Please die.
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.
yhbt yhl hand
I can tell she's into BSD.
yeah, she does look like a nercophiliac
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.
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.
.
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
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.
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 "
Somewhere, in a lonely hospital room,
*BSD is dying
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 distracted by the politickers
Yet another cunting bombshell hit the "community" of *BSD asswipes when IDC recently confirmed that *BSD accounts for less than a fraction of one single puny fucking percent of all servers. Coming hot on the heels of the latest Netcraft survey which plainly states that *BSD has lost more fucking market share, this news serves to reinforce what we've known all along. *BSD is ingesting itself backwards, disappearing up its very own shitter, as fittingly exemplified by coming a piss poor dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a cock-sucking 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 fucking future at all for *BSD because that sorded, shit-filled, mutated testicle of an operating system is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink splashes across the accounting documents like a series of exploding bloodfarts. FreeBSD munches the most ass of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD cuntwipes Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying and its rotting corpse smells worse than a maggot, vomit, shit and piss cocktail.
Let's keep to the facts and look at the fucking numbers, shall we? OK!
OpenBSD wanker Theo states that there are a pathetic 7000 users of OpenBSD. How many users of NetBSD are there? Oh, God, let's fucking see... The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore it's turd-suckingly obvious that 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, by simple fucking arithmetic, there are (7000+1400+700)*4 = 36400 FreeBSD users. Surprise fucking surprise, this is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of those arseholes at Walnut Creek, abysmal sales and so on, FreeBSD showed themselves to be a bunch of retarded tossers, went out of business and were taken over by BSDI who sell another special needs OS. Now BSDI is also a miserable failure, its corpse turned over to yet another charnel house... pathetic.
All major surveys show that *BSD has steadily fucking declined in market share. *BSD is where it belongs, at death's door and its long term survival prospects are almost non-fucking-existant. If *BSD is to survive at all it will be among moronic, dilettante shitheads. *BSD continues to Chew Satan's Dick And Fuck The Baby Jesus Up The Pooper. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD IS A FUCKING USELESS WASTE OF BITS AND IS DYING LIKE THE DOG THAT IT IS. IT MAKES ME SICK JUST THINKING ABOUT IT.
you fell for a blatantly obvious troll!
you fell for and actually spent time replying to a blatantly obvious troll/
*BSD lusers are so insecure about their own operating system that they have to come out and defend it whenever someone pokes fun at it.
no you lose. you were trolled, you took the bait, and you replied!
YOU LOSE, BSD FUCKER
by mere existance and use of *BSD
1) I wrote it while bored at work.
2) It took me 5 minutes to compose.
3) Of course it is all bullshit.
4) I first posted it using Mac OS X (oh the irony)
5) It seems good at hooking in the BSD zealots.
6) I am pretty ignorant of *BSD.
7) Don't take it seriously.
The FreeBSD platform in general is very unreliable, and many many problems have been reported over the last week alone. One appears to be a stuck interrupt, but all that code has been redone for SMP support. Why do they bother? SMP SUCKS on FreeBSD.
flask of ripe urine
pressed to freebsd lips
bsd drink up
Hope this was of help.
Eh? And Windows 95 had USB before FreeBSD. Does that therefore make it a better OS?
I find it entertaining when you BSD fans use such things to advocate your OS. I mean, just because a solid Linux distro is just as fast, reliable and well-documented as FreeBSD, but also offers much broader hardware support, software options and commercial support vendors (ie 5 yrs for RHEL over FreeBSD's pitiful 12 months), doesn't mean you have to write such nonsense.
And what's this "less fragmented"? All distros share the same code. Meanwhile, the FreeBSD project just kicked out one of its most talented coders -- Matt Dillon -- who's gone on to start YET ANOTHER BSD fork. Great stuff, that.
At the end of the day, Linux offers more than FreeBSD. Get over it.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even MicroEmacs 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 machine's 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.
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.
Consider that because of the many 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 infinitesimally 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.
NO YUO
All in all 5.2 seems a very lively corpse. Maybe the trolls are just the shallow end of the Linux Fanboy gene pool?
BSD is starting to speciate like Linux - instead of distros we see forks at a more fundamental level - first the Free/Open/NetBSD versions, and now we see a FreeBSD fork in DragonflyBSD and I see this new ekkoBSD, but I don't know why of the big three is its parent.
It is a good time to be a FreeBSD admin - gives me lots of free time via its stability, so I am working on a customized Knoppix that will allow me to whack a couple of hundred M$ desktops in 2004
I am very easy to get along with, but I don't have time to waste being nice to people who are being stupid. -Theo
Pretty much sums it all up, don't you think?