Slashdot Mirror
FreeBSD Freezes Code For 4.7 Release
SirGeek writes: "According to
the Daemon News and the FreeBSD site a code freeze has taken place in preparations for the impending 4.7 release on October 1st."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
It's not dead, its just frozen.
is that a posthumous release ?
was that a posthumous comment ?
Editors, please look these up - this must be the third or fourth repeated article within the last week.
What we see depends on mainly what we look for. -- John Lubbock Now search for that bug slave!
_WHAT IS NEW IN 4.7_?
im not too sure whats new, but i hope they have improved jail mgmt. As per the release schedule, the 4.7 PreRelease was out as of the first of sept! And as far as i know, the releases will come out 1 per quarter.
sideone
ITBitch.com - Your reason for leaving work
sideone
ITBitch.com Your reason for leaving work!
Please keep in mind that it will not be released until at least the 2nd or 3rd week in October, as per the usual release lateness.
[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 that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
hey muthafuckas, I TRICKED YOU!!!!
fuck slashdot! hizzy!
Many companies here in Toronto have dumped massive amounts of Token ring cards and switches. a 16mpbs pci card manufactured in 98 costs $2.5 and a 16 port switch costs $14. Massive reason for their drivers to be ported to FreeBSD. For now i'll just let the internet thru my freebsd nat firewall, then into the debian box into the switch and over to other computers. and hey the total latency chopped off here is about 2-5ms.. acceptable
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Is there any substantial basis for the slew of "bsd is dying" posts? Is this based on any current and tangible information? Or is it simply based on OS jealousy and the simmering resentment that Linux users may feel over the BSD-based OS X taking developer mindshare and media spotlight away from Linux?
In short...what's the basis for this?
Another 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
I think you misspelled "rigor mortis".
They think they're saving money, but they're really not.
Remember, nobody ever got fired for buying genuine Microsoft Windows!
Is the last release before FreeBSD 5?
The World is Yours.
Maybe in 50 years, cryonics will have advanced to the point where both can be revived. Until then, R.I.P. *BSD.
Cool, FreeBSD 4.7 will hopefully be released on the 1st of October this year :)
The main improvement I want to see on this version is the ability to do a net install on my laptop using a Xircom CEM33 pcmcia ethernet card.
Pity the Xircom project has pretty much closed, it was my last best hope, one of these days I should just go buy a better ethernet card, or maybe a CD-ROM.....lol
Saying your OS is the best because more people use it is like saying MacDonalds make the best food
Is anyone currently writing the drivers for the IBM serveRAID? I've had a look through the linux drivers, but it's so far above my head I can hardly see it.
Does anyone know if support for the SX-6000 controller will be included?
According to this mail from Søren Schmidt, he had added them to current in July.
I am not too familiar in how it works with the updates.
I saw that 4.6.2 could see the driver, although as TX-100's think, but when it came to see the drives as one, it failed and the installation found no discs to install to.
my sig