FreeBSD 4.9 Code Freeze
lewiz writes "FreeBSD Release Engineering have announced that the code freeze in preparation for 4.9-RELEASE (scheduled for 29th September) will begin on 25th August. Also 4.9-RC is tentatively scheduled for 12th September. A full list of dates can be found on the Release Process page."
The SCO is offering licences for the use of 0 and 1 in free bsd, at the low price of $699 per bit, with an increase to $1399 after October 15th.
*crickets chirp*
Cast:
Mr. Praline: John Cleese
Shop Owner: Michael Palin
A customer enters an operating system shop.
Mr. Praline: 'Ello, I wish to register a complaint. (The owner does not respond.)
Mr. Praline: 'Ello, Miss?
Owner: What do you mean "miss"?
Mr. Praline: I'm sorry, I have a cold. I wish to make a complaint!
Owner: We're closin' for lunch.
Mr. Praline: Never mind that, my lad. I wish to complain about this operating system what I purchased not half an hour ago from this very boutique.
Owner: Oh yes, the, uh, *BSD...What's,uh...What's wrong with it?
Mr. Praline: I'll tell you what's wrong with it, my lad. It's dead, that's what's wrong with it!
Owner: No, no, it's uh,...it's resting.
Mr. Praline: Look, matey, I know a dead operating system when I see one, and I'm looking at one right now.
Owner: No no it's not dead, it's, it's restin'! Remarkable OS, *BSD, idn'it, ay? Beautiful kernel!
Mr. Praline: The kernel don't enter into it. It's stone dead.
Owner: Nononono, no, no! It's resting!
Mr. Praline: All right then, if it's restin', I'll wake it up! (bashes at the keyboard) 'Ello, Mister *BSD! I've got a lovely fresh kernel update for you if you show...
(owner hits the keys)
Owner: There, it spewed some debug output to the command line!
Mr. Praline: No, it didn't, that was you hitting the keys!
Owner: I never!!
Mr. Praline: Yes, you did!
Owner: I never, never did anything...
Mr. Praline: (yelling and typing into the console repeatedly) 'ELLO COMMAND PROMPT!!!!! Testing! Testing! Testing! Testing! This is your nine o'clock cron job!
(Rips out hard drive from computer case and thumps it on the counter. Shoves it back inside the case and reboots the system - blank screen.)
Mr. Praline: Now that's what I call a dead operating system.
Owner: No, no.....No, it's stunned!
Mr. Praline: STUNNED?!?
Owner: Yeah! You stunned it, just as it was finishing an I/O task! *BSD stuns easily, major.
Mr. Praline: Um...now look...now look, mate, I've definitely 'ad enough of this. That operating system is definitely deceased, and when I purchased it not 'alf an hour ago, you assured me that its total lack of responsiveness was due to it bein' in the process of recompiling itself after a particularly comprehensive code update.
Owner: Well, it's...it's, ah...probably pining for some dilettante dabbling.
Mr. Praline: PININ' for some DILETTANTE DABBLING?!?!?!? What kind of talk is that? Look, why did it fall flat on its back the moment I started Emacs?
Owner: *BSD prefers swapping everything out to the hard drive! Remarkable variant, id'nit, squire? Lovely kernel!
Mr. Praline: Look, I took the liberty of examining the system when I got it home, and I discovered the only reason that it had been printing any text at all to the screen was because of all the WORRYING COMPILER WARNINGS encountered while it was being rebuilt.
(pause)
Owner: Well, o'course it was spitting out those warnings! If I hadn't updated the kernel with an unstable development build, you might have had your FTP server compromised, and VOOM! Bye bye to your business.
Mr. Praline: "Server"?!? Mate, this OS wouldn't "serve" if you put four million volts through it! It's bleedin' demised!
Owner: No no! It's pining!
Mr. Praline: It's not pinin'! It's passed on! This OS is no more! It has ceased to be! It's expired and gone to mee
Most of us FreeBSD fans will be far more excited when FreeBSD 5.x becomes stable, and has things like KSE enabled by default. 4.x is a aging branch with only limited whiz-bang appeal.
Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
9994Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
8498Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
27312Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
22801Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
6196Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
9712Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
21255Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
14884Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
13252Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
4375Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
6646Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
1054Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
28028Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
12178Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
369Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
26861Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
18518Poul-Henning, asshole extraordinaire, has managed to ruin FreeBSD with his new GEOM and devd ego trips, that will silently rot, while he doesn't let anyone else touch them. FUCK YOU POUL. Long live to DragonFlyBSD!
Turbo Glass
6625[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
It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.
Fact: *BSD is dying
It is common knowledge that *BSD is dying, that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The erosion of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.
Fact: *BSD is dying
It is common knowledge that *BSD is dying. Everyone knows that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.
Fact: *BSD is dying
First thing that i like to say is that I pee for pleasure on the people that always say *BSD is dying. These people will crawl back to *BSD because soon linux is dying because of some lame ass SCO crap.
Check my site: http://pixel.pagina.nl
1. It is dying
2. It has no GUI
3. It is fragmented
4. It is associated with SCO
5. It has no games
6. It is run only by geeks
7. It is unusable by Grandmas
8. It has fewer than 500 users
9. You can not install it on a pentium
10. You cannot apt-get it
4.9 Release notes showing what is going in/being fixed
Rus
Cheap UK and US VPS
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.
This bitch is dead.
Some dork, obviously an ex-freebsd disgruntled lame wounded spammer is managing to get around the multiple post of the same shit lameness filter. So it is time to make the lameness filter a little tougher to get around. The moron will tip off the MS sponsored GNAA people and bingo some idiot will write a script that will take down /. Time for affirmative action against scripted bot posts. Make a longer interval on post acceptance and a diff with the last post blocker. Then start kicking the users off that do that kind of shit until they are willing to send e-mail appologies to the /. gods before they are permited to post from a given location again!
OH THE SHAME I fell off the wagon and use sigs again!
I was wondering, can any of the people who seem to be badmouthing FreeBSD all the time code? If so, have you contributed at least a line of code to making your much beloved Linux better? If so... Wait a minute, I'm talking to myself now.
Seriously though, if you are not contributing in any way, but still think that just being a fan makes you superior to other teams and their fans, you should think about this: the game is not about you, you're just observers and if your team should cease to exist, you wouldn't know what to do with a football to save your life. So put your scarf on, cheer like a good sport, but leave the criticism to those who actually play the game.
Rather they are a balanced point of view, based on my personal experience.
:(
Now please run along and drink your hot chocolate...
Damn he is right about point 2 though
Only fags use 5.1.
Now there is something that Linux can't claim. An operating system *SO* easy to use, that cigarettes can use it.
If a mindless cig can use FreeBSD 5.1, is Joe SixPack far behind?
Set your minimum score setting to 1. End of problem. Anyone who can't be arsed to log in and can't write anything interesting enough to get a moderation point from someone is no loss.
_O_
.|< The named which can be named is not the true named
Are you *BSD lusers getting the hint yet?
P.S. *BSD looks like it stole some SCO code - get ya credit cards ready.
Searched the web for *BSD is dying:
Results 1 - 10 of about 12,100. Search took 0.28 seconds
That is a lot of dying, genocide levels.
This is concrete proof that *BSD is dying. After all, Google knows everything.
I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.
BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.
Elegy For *BSD
I am a *BSD user
and I try hard to be brave
That is a tall order
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
I read somewhere they will continue untill 4.12:
4.9, 4.10, 4.11 and 4.12 = VERY STABLE
The 5.X branch should become 'just' STABLE by then.
FUCK YOU --- NO, FUCK YOU -- NO, FUCK YOU
jesus h motherfucking christ...
GROW UP YOU WHINING LITTLE BITCHES
mod this as a troll.. i don't give a fuck..
You all are just a bunch of whiny little bitches with your 'fuck you -- no fuck you' bullshit..
What the hell ?!?!??
Are you all stuck in some white trash/ghetto high school or something ?!?!? -- YOU SURE FUCKING ACT LIKE IT!!
iF yOu WAnT to C YOUr iP agaIn gAThEr tWO MilLIon dOLLArS IN Non - cONsEcuTivE TweNtY's AnD AWaiT FuRThER iNstrUctIoN
That's interesting. A recent Netcraft survey showed that there were thousands of FreeBSD IPs. Over 40000 alone at Yahoo. Extrapolated, every single person who even visits Yahoo is a FreeBSD user...
Do not meddle in the affairs of dragons, for you are crunchy, and taste good with ketchup.
I'm interested in trying out FreeBSD or any of the other BSD operating systems. My one main concern is backups. There are a whole slew of backup solutions for Linux, mainly LVM and filesystem snapshots comes to mind. LVM also allows you take incremental snapshots which is a big plus for me. I heard in #freebsd on irc.freenode.net that FreeBSD 5 has filesystem snapshots but no incremental =(
And another thing. Are there any plans in the future of the FreeBSD project where binary updates will be officially supported instead of doing make world whenever security patches need to be applied? I've heard that the argument used against any binary updates is security and how trojans could be slipped in. Couldn't this be avoided if each binary update tarball was signed using the FreeBSD release engineer's gpg key?
I can't understand a word of what you wrote. And somebody modded you up?
Simple us poor suckers that keep a zero threshold need some temporary protection against the idiots that are doing a number on the bsd posts. It is getting to be a pain in the ass that the good people who contribute to good old bsd have to put up with more than a fair share of bullshit. If you do not agree with that then use hot mail and suffer the consequences when MS tries to migrate the server to 2003 again. Freebsd, and other bsd varients and the community that write for it are GOD DAMN important to OSS, linux and the future of internet communication. OSX for Apple would not exist without it and Microsoft would have squat left to reverse engineer, or clone. Just think MS would then have to be innovative, a f'in impossibility!
OH THE SHAME I fell off the wagon and use sigs again!
I'm pretty sure that it has been decided that 4.10 will be the end of the road. Also, as the version minor increases, the difference between it an the previous version decreases. That is, by the time we had a 4.11/4.12, the unified diff would probably be only a hundred lines long...
Saying "good old BSD" was a very big mistake.
404: Parent Post punctuation not found.
It is common knowledge that *BSD is dying. The IT community is keenly aware that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of BSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major marketing surveys show that *BSD has steadily declined in market share. *BSD is extremely sick and its long term survival prospects are infinitesimally dim. If *BSD is to survive at all it will be among hobbyist dilettante dabblers. In truth, for all practical purposes *BSD is already dead. It is a dead man walking.
Fact: *BSD is dying
Ok, since I'm something of a neophyte, I'm going to show my ignorance and ask, what are the big differences between *BSD and linux. I know they're related. I've been under the impression that they share a relatively wide variety of software. With BSD being thought of as more stable, and linux a little more flashy with some of the software, like wine x, available for it.
Please disabuse me.
--Jimmy has fancy plans; and pants to match.
PAE-physical address extensions, ported over from 5-CURRENT. I wonder if they're going to put out a version 4.10, because PAE doesn't yet work on all the drivers in current much less all that many drivers in 4-STABLE.
I can see its demise. It will fall, yet know one will notice.
*BSD - as dead as my grandma.
Are you *BSD lusers getting the hint yet?
P.S. *BSD looks like it stole some SCO code - get ya credit cards ready.
My original line for lameness
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.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD 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.
Troll. Seen it before.
Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
Parent has nothing to do with topic
Get over it, Craig. For all practical purposes, FreeBSD is already dead. It is a dead man walking.
Yes, if there were a God then I would thank her. I would thank her that I don't have to go through my short life imprisoned inside of a mind with a viewpoint anything remotely resembling yours.
[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
_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
FreeBSD Frozen: Does that mean it is finally dead ;-)
Oh well, looking forward to the 5.2 release, however, it is good to see that 4.x series are continuing to be developed as the temptation by some uname groups to focus more on the sexy/cool version rather than the boring maintainance work that is required.
"The difference between pornography and erotica is the lighting" - Woody Allen
_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
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 the open-source community. 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.
[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