Slashdot Mirror
New Testing Version Of Linux 2.6
James A. A. Joyce writes "It's all up now at the kernel archives. Get the full 2.6.0-test2 or a patch, whichever suits you. We need to test those new kernels! Hop to it!"
← Back to Stories (view on slashdot.org)
Linux suxors! (don't mind me, just adding to the noise)
So you think they'll finally have USB support added to Linux so I can just plug in my digital camera and have it work instantly, like in Microsoft(r) Windows(r) XP Professional or MacOS X?
Hi,
I'm the Bob Goatse, can you add me to your mailing list. Thanks.
My name is GoatSe.CX my e-mail is GoatSe.CX.
11111!11 WTF LOL I DONT KNOW .1!!111!!1!11!!1!1!!1! OMG YALNG FILT3R? .1111!!!1!!!!1!!!! WTF IMM ON AOL!
2?!!!!!!??!! OMG LOL NOPA
31111!1!!1!! LOL Y3S11!!1
I just built and booted it on my Sun Ultra 60. CONFIG_PREEMPT seems broken on SPARC64, but after I removed a redefined symbol in ffb_drv.c, everything else seems to work.
Beautiful. Hack here and there, code away without a plan until it "seems to work". This is basically the mentality behind linux coding. Famous quote:
Some systems seem to have the philosophy of "If it works, it's right". In that light NetBSD could be described as "It doesn't work unless it's right".
I know why I never look back and don't even miss it.
[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
Now if they'd only get rid of that BitKeeper crap, with the project leader that insists on trying to screw us at every opportunity, we'd be set.
You're a fucking insensitive little cock sucker. I hope your mom gets raped by some nasty negro jail breakers and pray to god that this happens to your dad
DO NOT1 TYPE1 EMERGE1 HOTPLUG111111!!!IT WILL L11OAD GOA4TS1E AS Y11OUR WALLP11APER AND CA11NNOT BE REM11OVED1!!!11111
11
111111111111111
That's what the web stats always said BEFORE slashdot went corporate.
It's quite embarassing that ONLY 5% of your user base, ON A PRO-LINUX SITE, uses Linux.
What it shows is, that Slashdot is a site where loosers TALK about Linux, not actually use it.
As one last note, the 5% statistic is the Worldwide average of Linux users is.
FreeBSD is dead. Linux is dead. Mac OS X is the future. Think Different. Think Better. Think Apple.