Slashdot Mirror
DragonFly BSD Announced
JoshRendlesham writes "Matt Dillon announced today on the freebsd-hackers mailing list the creation of the DragonFly BSD project. It seeks to build on the work of FreeBSD 4.x, including a rewrite of the packaging and distribution system, among other goals."
hey guys I'm going to reivent the wheel again durrrrr.
ISO Plz!! k THX!!111
Instead of different BSDs that are similar, how about combining the best into one unified BSD, like with Linux. There is only one official Linux kernel, and distributions are based upon it.
...and counting. Good thing Dubya 'restored dignity to the White House', eh?
Wake up, folks, do we want another 4 years of this (lies and warmongering)?
As the rest are dead or dying, would this one be stillborn?
First person to post the "BSD is dying" troll gets a nice big KNUCKLE SANDWICH!
"Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
MS Windows is a BSD? Am I missing something? /me checks out c:\winnt\ports
"Quoting famous computer scientists out of context is the root of all evil (or at least most of it) in programming." - K
what do cocksmokers think about this development?
what do porch monkeys think about this development?
what can we learn from the above?
*BSD is still dying? :)
Hi. I have oral sex with retarded kids. Retards are yummy.
/*
**
** I.H.O.S.W.R.K.
**
*/
I think in the case of Windows, BSD = Blue Screen of Death. Your parent poster was probably just confused.
I don't want to start a holy war here, but what is the deal with you FreeBSD 4.x fanatics? I've been sitting here at my freelance gig in front of a FreeBSD 4.x(a 8600/300 w/64 Megs of RAM) for about 20 minutes now while it attempts to copy a 1GB file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this Mac, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even BBEdit Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various FreeBSD 4.x, but suffice it to say there have been many, not the least of which is I've never seen a FreeBSD 4.x that has run faster than its Wintel counterpart, despite the FreeBSD 4.x' faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 300 mhz machine at times. From a productivity standpoint, I don't get how people can claim that the FreeBSD 4.x is a superior machine.
FreeBSD 4.x addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a Mac over other faster, cheaper, more stable systems.
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 [samag.com] in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin [amazingkreskin.com] 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
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. I
O! What are you seeking?
/. and JRRT have in common -- suck-ass poems that interrupt the narrative
And where are you making?
The faggots are reeking,
The bannocks are baking!
O! Tril-lil-lil-lolly
The valley is jolly,
Ha! Ha!
What
Black men scare me!
You must be a hoot at parties.
In all honesty, we both have to admit that BSD is pretty much dead. It's time to move on.
Speaking for cocksmokers everywhere I can wholeheartedly say, "We like it!"
Your Pal,
Mister ShortPants.
- Windows is viable.
- BSD is dying
There you have it in a nutshell.Put that in your pipe and smoke it.
Buddy, you need a bop from the cluestick: BSD is dying
In all honesty, we both have to admit that BSD is pretty much dead. It's time to move on.
You said a mouthful. BSD is dying.
- Theo
*BSD users should start making transition plans. One or two years more and that's all she wrote for *BSD.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will only be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
It's dead Jim. Bury this BSD bitch before it stinks up the joint.
[Ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. I
Fact: *BSD is dying
[ Note: in this 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
BSD is the offical OS of all cock smokers and cum guzzlers.
BSD mean death. It is a dead operating system. Unless you make it your hobby. Woot.
In Soviet Russia BSD is also Dying.
My name is B - S - D.
BSD is headed for the last round-up, pilgrim. It's ridin' up that
lonesome trail to meet the big VAX in the sky.
Subject says it all.
A Day in the Life of Michael Sims
06:00
Alarm goes off, Michael slaps the sleep button.
10:00
Michael finally wakes up and starts making breakfast: 16 Reese's peanut butter cups, 1 gal. 2% milk, "Big Grab" Fritos, four cold hot dogs, and coffee.
10:45
Time for email! Michael opens Outlook Express 6 (*gasp* Michael uses Windows!? Yes, the truth hurts, folks.) 30 emails from known trolls bitching about moderation bugs and abuses, 20 additional emails from trolls incognito regarding Slashdot censhorship, and 5 emails from legitimate Slashdot readers regarding bug fixes and code patches.
11:15
Lunchtime! Michael has a triple-decker balogna sandwich and Nacho Cheesier! Doritos. Washes it down with Nestle Quik! Strawberry milk. Finishes it off with a healthy swig of Pepto-Bismol and a few Tums.
11:45
Michael opens Emacs and starts coding in Perl: SLASH has a lot of bugs to fix, thanks to Taco. Michael silently curses Taco under his breath. Feels underappreciated, overworked, underpaid-- oh wait, Open Source software unemploys programmers. Michael wants to bitch but knows he can't.
11:47
Quits Emacs, opens Pico. Can't handle that "complex shit" anymore.
12:10
Calls ex-girlfriend, cries into phone for 10 minutes before realizing she'd hung up on him seven minutes ago. Questions his manhood. His manhood does not respond. Sad little knob, it's gone neglected for years.
12:30
Shower time! Heads down to the local truckstop, grabs a ticket for a restroom, and hopes the door locks. In the middle of his shower he is accosted by the janitor (again). He supposes the door didn't lock. Screams go unheard and the janitor walks away satisfied. Michael cries in the corner of the shower stall for a a while before running home, still crying.
13:00
Back in front of his Pentium II system running Linux, Michael masturbates while thinking of being raped by the truckstop's janitor in the shower. Though terrified at the time, Michael feels exhilerated by it in general. Michael fingers his asshole to bring himself to orgasm.
13:01
Conference call with Rob "CmdrTaco" Malda, ESR, and Michael. How do we silence the trolls? Michael suggests deleting comments and accounts regularly. ESR and Taco, however, know this would be bad for business-- they own stock in the company! Michael is frustrated and hangs up on the call.
13:30
Time for more food. Even though Michael eats enough for three geeks, he has a rare disorder that increases his metabolism. Michael is 6'2" but only weighs 120lbs. Michael is eating pickles, celery wih peanut butter, cold baked sweet potatoes, and dog food. Michael is too hungry not to eat whatever is in sight.
14:00
Returning to Pico, Michael begins working on tweaks to the moderation system, purposefully coding "features" so the likes of Mighty-Troll, Trollaxor, and the Turd Report will be silenced for being funny and creative. Michael can almost see their emails, bitching about being banned.
15:45
Michael begins getting itchy. The rash is coming back, so Michael strips out of his clothes and sits naked. Nearby plants in his condo wilt and die, milk curdles, and Linx begins core-dumping. Michael is ashamed. He cries as Linux reboots and wishes the rash would leave his pale, skinny, feminine body.
16:30
Michael declares "quittin' time" now as he's had a very stressful day. He needs some time alone so he works on the holocaust project. Thousands of Jews laugh at him for having naively fallen for the greatest lie in all of history.
17:45
Michael gets the mail. New Playgirl. Next few hours blown.
21:00
Raw, chafed, and sore, Michael passes out on the couch naked after a marathon session with the new Playgirl.
23:50
In a zombie-like trance, Michael stumbles off to bed and falls back asleep, preparing to do it all again tomorrow.
BSD is as dead as an AIDS homo sucking on a cyanide coated
70 KVolt high tension cable with a ground wire shoved up his ass.
BSD commissars are always spouting some kind of socialist gobbledygook. The free market said "No! we don't want BSD!" "We don't want to give away our work with no recompense!"
Take your BSD socialism and shove it up where the sun don't shine!!!
Oh wait, the show "Six Feet Under" is what I was thinking about.
*BSD: as cold and stiff as a porn star in Sweden.
Ouch. It hurts 'n' stuff.