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."
Kernels recompile you!
FreeBSD should've died on Verona 3. Truly.
Frosty toasty holiday posty!
w00t to your mother, as AC Hammer might have said.
Hey who is the OSDN hottie in red? question mark question mark question mark
A BSD download and personals ad doesn't mix ...
or is it the work of a d(a)emon ?
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.
I have always loved open source projects.. this has a unique opportunity of researching on your own and learning what others have done on the research.. like simple scalar tool available on University of Texas austin that allows you to research on microprocessor design I consider this one is a nice research tool in OS. Crossing my fingers for this release.
/. just cannot resist the chance to take a shot at FreeBSD over a kernel panic in the story, can it? One stability issue in FreeBSD in what, 5 years?
/. editors obviously have it in for all the *BSDs. The only reason there is a BSD forum at all is so the editors can take potshots at it and make Linux look better by comparison.
Yet, the myriad of kernel panic issues in Linux go conveniently ignored. When is the last time you've seen a Linux kernel panic mentioned on the front page? Answer : You haven't.
It's piece of shit. Dead meat. Tannenbaum already commented it is worth nothing. *BSD is a dead man walking.
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)
That means that the next two releases on the 5 branch are going to be last times new features are added to the branch before -current forks, so it's going to require a lot of testing to ensure stability.
Why do you care?
Well, if you don't ever plan on using FreeBSD, you don't. If you do use FreeBSD, tossing this release on your hardware and making sure things like ACPI function with your motherboard are really important as NOW is the time to fix them so that they can be tuned and maintained prior to the 5.3 Release when the code is marked stable.
The major changes in FreeBSD 5 are significant. There's new locking throughout the tree, which should improve SMP performance everywhere. There's also finer grained locking in the Network stacks (thanks Sam), better ACPI (thanks John), support for AMD64 (coming slowly, thanks Peter), and the GEOM disk abstraction layer (nice work PHK), which has already been shown to be useful for things like GEOM-gate (a la nbd in Linux), is getting more mature with every release.
Performance and stability
--
Use Vobbo for Video Blogs
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!!!!
[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
FreeBSD corrupted my HD!! That was the last thing!!!!! Never gonna touch that piece of shit again!!!! Stick with OSs that work.
RC# isn't news, certently not front page news. now FreeBSD 5.2 RELEASE would be.
An HP ProLiant DL140 server, apparently.
Oh wait, you've probably got a different ad...
- 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.
Perhaps this "bais" is due to the fact that Linux kernel panics are not news. However, kernel panics in BSD are so rare that when they occur they are indeed news.
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.
And yes, before the Linux hordes flames me to death, yes I know that Linux kernel does have Opteron support and has been more or less 64-bit compatible since the DEC Alpha days.
I'm talking about the distribution. I am considering buying a dual Opteron in January but all the Linux distros seem to be betas. A quick search on Google reveals that the distros have serious problems. In particular, X doesn't work and compilers fail completely.
FreeBSD reports Opteron as tier-1 hardware, so how is it?
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.
Anybody who hasn't tried 5.2 RC2 yet is really in for a treat...
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.
(BEGIN RANT)
So you expect other people to fix it for you for free, eh?
I don't know about the rest of you, but I think this particular attitude is becoming a real problem in the free software community. Fucking tech-illiterate lamers wishing to run Linux because it's "cool" and then when they run into a little bit of trouble: "Does it work?", "Why doesn't it work?", "Why should I have to do anything about it?!". Whine, whine, whine, bitch, bitch, bitch.
Hello! It comes with SOURCE CODE! You can either shut up and go back to your favourite toy operating system (Win-hell or OSX) or grab that piece code and fix the goddamn problem yourself.
We're quickly turning into a community where the minority consists of the hackers that attempts to pander the majority of PHBs, lamers and wannabes. Stop pandering them. Give them some code and tell them to put up or shut up. We don't need freeloaders here.
(END RANT)
Wasn't 5.2RC2 just released?
> bugs, specifically the one in which users
> experienced system panics during install
I wonder how they expect anyone to actually use an operating system whose installation procedure makes experienced users panic... Oh, yeah; I forgot. It's open source.
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.
What's the status of pf on FreeBSD? And what's the preferred packet filtering/firewall setup these days?
The last I checked, circa 4.8, you had to recompile the kernel just to get a NAT "router."
Has NAT-ing and filtering drawn any attention in the 5.x series?
I ask because FreeBSD has about the best host adapter/hard drive support in the business [possibly better even than NetWare] - if you've got an old hba and an old hd, FreeBSD will load the drivers and do the LBA translations to perfection. I've seen countless motherboard/HBA/HD combinations where e.g. Windows 2000 just can't get the LBA translation right. Or OpenBSD, for that matter.
Which brings me to the question of Theo. Since I'm interested in NATing/PFing/SSHing, most people would say, "Then you want OpenBSD," to which I say, Yeah, some of Theo's goals are laudable, but, quite frankly, the guy's a kook, and guts of his operating system don't work all that well.
I'd rather use something designed by grown-ups.
"Peace on earth, good will to men!" to you too...
"NOW is the time to fix them so that they can be tuned and maintained prior to the 5.3 Release when the code is marked stable..
Shouldn't this read something like:
NOW is the time to fix them so that they can be tuned and maintained so that the 5.3 Release can be marrked stable.
In other words, the code should be marked stable when it IS, rather than at some arbitrary release level.
I want to delete my account but Slashdot doesn't allow 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.
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.
that's the best part IMGO: "Scott is asking everyone to test this release over the holidays". What a scary geeks you are !
I re-iterate. -STABLE is *NOT* the most stable branch. It is not comparable to 2.4 in Linux. For more information, please see http://www.freebsd.org/handbook/current-stable.htm l (which explains the -CURRENT and -STABLE branches as well as a bit about releng.)
;))
But yes, thanks to the developers who have been working on this. And thank heavens that it's the holiday season; now I'll finally have time to work on locks in the IPv6 stack (thanks Sam and Robert
www.sitetronics.com/wordpress
It's dying!
OK, It's so much that it's dying .... it's that all these companies like SCO are able to keep living by forking off endless proprietaty code for themselves because the FreeBSD license allows it. Do a "strings" command on any SCO binary and you'd be amazed how much similar stuff they have to the FreeBSD equivalents. (what's even more amazing is that for all that copying you'd think they'd be able to make SCO stable)
OSDN now has a *BSD Dating Service
Please try to keep posts on topic
.
.
Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
Scott is asking everyone to test this release over the holidays.
Is this an example of copying the Microsoft practice of having the customers perform the actual testing?
_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.
BSD itself died, back at v4.4 when UCB stopped doing development itself. The body parts have been transplanted into computer systems all over, almost every system has some BSD code.
The current BSD's are like the children of the original, taking on the family business.
BSD is like the late, great, patriarch, whose portrait hangs on the wall, in the living room of the family mansion.
With *BSD proving to be especially resilient, *BSD trolls are facing the reality that *BSD is, indeed, not dying after all. The particularly outspoken troll known only as "Anonymous Coward" recently said, "*BSD trolls will never die, like *BSD soon will! We will never give up! Face the death of *BSD and switch to a different OS and section!" but the numbers tell a different tale. In fact, in the month of December alone, *BSD trolling is down by 14%, continuing a pattern from earlier months. *BSD may not be dying after all, but it seems to be only a matter of time before the *BSD trolls' days of trolling the BSD section are over.
Fact: *BSD trolls are 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.
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.
19996Back 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.
22902Like it or not we - as a community - need the masses if free software is to survive. Elitist luddite assholes ("we don't need standardized gui" etc.) like you are the cancer holding Linux back.
Netcraft now confirms: *BSD is dying.
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 further 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.
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
"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?
An HP ProLiant DL140 server, apparently.
Oh wait, you've probably got a different ad...
For sex appeal, pretty much anything beats the geek I'm staring at. Apparantly he's using his UNIX experience to administer Windows Server 2003.
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
For those of you that have been neglected by the gods or ad rotation, look here. (Do you think the red ad was designed to match the /.-BSD theme?)
Whoever she is, I can tell she's into 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.
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.
19699Back 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.
18030Back 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.
7867What I really wish for is private Sys V IPC and multiple IP's for jails to be available as standard features. Currently, there are some patches out there, but they seem outdated.
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.
18744Back 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.
9268Back 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.
24956Back 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.
28245Allowing freedom includes allowing people to do things you don't necessarily agree with. I used to defend the GPL consistently, but I'm starting to feel like "Free as in Speech" should also include unpopular speech, and that's what the BSD license protects that the GPL does not.
...software which OpenBSD uses and redistributes must be free to all (be they people or companies), for any purpose they wish to use it, including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia.
In the words of Theo de Raadt:
As opposed to the the GPL, which exists as Stallman's attempt to redefine "Free Software" as any software that suits his political ideology.
The GPL as a strategy is fine, but to call it "freedom" is less than honest. Whose freedom is being protected by the GPL? The developers? Not really. The developers are only allowed to use the source as long as they conform to the RMS ideology that the work they do should benefit the collective and not necessarily just the individual who wrote the software. As for the users, what freedom do they gain by using GPL software over BSD licensed software? The freedom to use software that does not co-exist peacefully with others? The freedom to view the source code they don't understand or care to understand? Besides, the original BSD software always remains free as in speech and beer, even if the Hated Proprietary Software Vendor of the Week exercises their right to protect their own interests.
I'm certain that I'll be moderated as a troll, but this something that I've been pondering quite a bit lately, and I'm certainly willing to be proven wrong.
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!
Are you listening, Neo? or were you looking at the lady in the red dress. And speaking of red, I'm glad the OS in the red devil(er... daemon) suit is getting opteron support.
read my blog
musings on politics and technol
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!
I agree with this post
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!
How much longer will 5.x wear the "New Technology Release" label?
--Brian
Puhleeze.
I had three BSD servers that would crash (sometimes often, sometimes sporadically) quite often that I had to switch over to Linux and NT.
BSD users outright lie about the OS.
don't you dare talk bad about *BSD.. you'll get modded down.. don't want that pesky truth leaking out, now do we?
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.
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'm looking forward to trying this release out; I've been using FreeBSD 5.1 for a few months and have been very pleased with both the startup time and the relatively little difference between it and Linux. I mean that from a user's standpoint of course, I know the internals are drastically different, but quite a lot of source compiles on FreeBSD pretty easily with little or no patching, and there's always ports to handle that, which, digressing, is an extremely great feature that I know other OSes have. Anyway, it's worth a try if you're looking for something new, and I don't think you'll be entirely disappointed.
It is perhaps anybody's guess as to which FreeBSD is the worst off of an admittedly suffering FreeBSD community. The numbers continue to decline for FreeBSD 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.
Every major marketing survey has shown that FreeBSD has steadily declined in market share. FreeBSD is very sick and its long term survival prospects are infinitesimally dim. If FreeBSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking.
Roy Horn of the famous "Siegfried and Roy" magic ensemble was interviewed today from his hospital bed. Mr. Horn is recovering from a life threatening tiger attack. When asked about his condition, Roy had this to say,
Hang in there Roy. We're all pulling for you!
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.
I personally feel that ipfw/natd are a terrible combination, and are confusing and frustrating to use, to boot. I have been able to do everything I need to ipfw/natd, however. My major complaints were:
1. Cannot dynamically reload rules of ipfw (your connection can be broken after a flush, and before new rules).
2. Poor (really no) integration of natd/ipfw.
3. Weaker rules/macros than pf.
The FreeBSD pf port is coming along nicely. I am currently using it with a kernel loadable module and a startup script, both of which are installed by the port. You do still have to recompile the kernel:
You need these options:
"device bpf" and "options PFIL_HOOKS"
The port will tell you to do this when you install it. My transition was very easy, and immediately I was happier with pf. I had never used it before, and I prefer it immensely. I use it to do firewalling and NAT, and they are integrated, of course.
So, I'd say the status is...good! I'd prefer not to have to rebuild the kernel, but I'm used to that by now.
-Dan
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.
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.
I had a problem with 5.2-RC1 where by on boot the kernel would detect the HDD and say [MPSAFE] and then pause for a while, this struck me as odd, mostly because i interperated MP to be Multi-Processor, and i was on a Uniprocessor machine (and thats an AMD, not an Intel P4 w/ HyperThreading, which i know is set up as a virtual CPU in the kernel for scheduling)
If anyone knows if this has been resolved, I'll probably update my box from 5.1 to 5.2-RC2 tonight.
As a side note, I'm curious as to what ports are broken, I've yet to encounter one that I can't compile under 5.x, including all the things I used to run under 4.x/3.x/2.2.x (yes i've had the same FreeBSD box that long)
Music is everybody's possession.
It's only publishers who think that people own it.
Fuck Beta
~John Lenno
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.
> Mastery of mspaint does not qualify you as an experienced user.
Perhaps not, but remembering that mspaint still exists might be a qualification in itself. That program seems as ancient as dosshell these days.
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.
...when properly set-up and not fucked up by incompetents like yourself, FreeBSD just runs and runs. I've never EVER had a FreeBSD box crash on me or otherwise not work. How? I read the fucking manual, thats how.
There are so many things in these new technology releases that I am so lookiing forward to implementing on my own machines once this branch becomes stable. GEOM Based Disk Encryption and LOMAC are among them.
The background fsck saved me a couple of times before I got UPSs for them, and the new GENERIC SMP kernel will be great once I get my new dual Opteron.
All in all FreeBSD is doing great, and I'll never go back to Linux; there's no incentive, nor need.
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.
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.
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.
Always has to take a potshot a Linux when its shown that *BSD Sux0rs
ever heard of a proxy?
it's that all these companies like SCO are able to keep living by forking off endless proprietaty code for themselves because the FreeBSD license allows it.
Now this would be the company that took stock market IPO money from its GNU/Linux offering and bought the USL code. The same USL that had chunks of BSD copywritten code in the USL tree where the USL people removed the BSD license and copyright and put on USL copyrights?
Your 'statement' ignores the past. But if it helps you feel better about yourself, keep thinking BSD licensed code is somehow evil, ok?
Well, I have to say, having just installed a FreeBSD (5.1) server in my house, I am blown away at the stability and easy configurability of this thing. I built the computer it is running on for $160.00 with (obviously) cheap parts and it is perfrominig like I had really spent some money on it. This was much easier to install software for and configure than any of the Linux distros I have used in the past, including the vaunted RedHat. Stable and fast. That's what I like, and this isn't even the current fork. :-)
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.
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.
flask of ripe urine
pressed to freebsd lips
bsd drink up
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.
- deal with the inevitable.
- grieve for your loss.
- move on.
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.
Always has to take a potshot at Windows when it's shown that Linux sucks.
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.
Why was a post detaling problems with BSD modded down, but a post that praised BSD and made unfounded cheapshots at Linux modded up?
And you guys wonder why you get trolled so much? Maybe if you folks weren't so uptight about your operating system and could have an honest discussion of the facts, you wouldn't be in this situation. But hey, you brought it upon yourselves.
you fell for a troll
Why was this modded down but the one above it not?
They're both WAY offtopic. Oh wait, its not about topic, its all about how much of *BSD's ass you kissed.
Sorry, I thought the moderation around here was fair and unbiased.
HAND
flask of ripe urine
pressed to dead bsd lips
bsd drink up
NO YUO
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.
I've recently switched from Debian Linux to FreeBSD 5.2. I was running a pair of RAID-1 arrays off a Highpoint HPT372 RocketRAID 133 controller using Highpoint's rather lackluster, "open source" driver. Of course, contacting them about FreeBSD support greater than 5.0 has yielded nothing useful, so now I am on the hunt for other solutions.
I've come across offerings from 3ware, notably the 7006-2. What caught my eye about this card (well, all of them from 3ware) was that it's actually a hardware-based ATA RAID adapter (where as RAID functionality is implemented in software for most ATA controllers out there). Does this mean that I can use this card without any driver hell? Will a RAID-whatever array simply appear as another /dev/a[dr]* device or is it not that simple? (By the way, I care little about CLI tools for rebuilding the array. I am content to use the card's BIOS to do management.)
Of course, if I can solve the problem with my Highpoint, that'd be useful too. Currently, if I create a RAID-1 array, the two real disks appear as /dev/ad4 and /dev/ad5 but I also get a /dev/ar0 device. However, if I simulate a disk failure, none of the devices appear. It appears to me like FreeBSD indeed supports the RAID functionality of this card out of the box, but a bit of minor tweaking is required.
The bottom line however is I wouldn't mind buying a a RAID adapter with functionality implemented in hardware. That'd be better overall. I just want to make sure it'll work with flying colors in whatever OS I choose to use.
Join Tor today!
notice how all the moronic posts saying BSD is dead come from anonymous posters, in other words people who don't have a pair and don't have any real arguement. take a look at netcraft you bozos and see if bsd is dieing. I use bsd, it's got a much more coherent design then linux and it's documentation is much much better. It's multimedia isn't quiet as good as linux yet but that hasn't been as much of a focus as for linux. In short if you think BSD is old hat and dieing your an idiot, nuff said.
If you mod me down, I will become more powerful than you can imagine....
FOAD
http://slashdot.org/comments.pl?sid=90450&cid=7806 876
all fluff, conjecture, no supporting evidence, and takes cheap potshots at Linux.
'nuff said
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.
Join the Jihad!
However, USB 2.0 (EHCI) is still not supported (to try it, add "device ehci" to your kernel configuration). This makes using portable hard drive enclosures under FreeBSD less than optimal, as transfers go at the slow 1Mbps of USB 1.1 instead of the much faster USB 2. No one seems to be working on ehci.c at the moment; Firewire portable drives currently seem to be a better option for support under FreeBSD.
Tired of free ipod spam sigs? Opt ou
No, not rocket science. Just ordinary common sense.
- 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.
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
"Don't moderate just answer the fookin' question."
It hurts 'n' stuff.