Slashdot Mirror
Linux 2.4.22 Stable Kernel Released
An anonymous reader writes "Marcelo Tosatti has officially released another stable 2.4 Linux kernel. 2.4.22 was released early this morning and includes a lengthy list of fixes. It follows the last stable kernel in this tree, 2.4.21, by a little over two months."
Is there such a thing? It's tiresome reading through all the changelogs (2.4.21 -> pre1 -> pre2 -> etc).
Thanks
"Would it kill you to put down the toilet seat?" -- Maya Angelou
Hint: The 2.4 maintainer is a student who gets the summer off. :-)
I wish we could charge the legal expenses for evaluating these types of things to SCO... their FUD costs us real money, especially when they're shown to be totally baseless.
Too bad that once that's proven, there won't be an SCO to recover damages from. Oh well...
MadCow.
I used to have a sig, but I set it free and it never came back.
Luckily, you probably won't be deploying Windows either considering there are at least two IP lawsuits going on against them and, contrary to their recent crowing about paying for legal fees, their EULA says that you would be liable in court should anyone decide to sue you for improper IP usage.
Considering the track records of Linux and MS, I tend to believe Linux is innocent while MS is guilty as sin.
That's what keeps linux off my laptop fulltime. I simply got tired of monkeying with patches and scripts in order to get all my hardware working the way its supposed to. When ACPI become pretty much defacto a few years ago I was pretty worried because the entire world was going ACPI and linux didn't even have anything going yet. Flash forward to now and this widely used feature is overall still MIA for linux. Basically its totally hit or miss if your machine will work with ACPI and that's a huge problem.
The problem from what I understand is there are so many iterations of it that the devs simply can't get the kernel to work with all of them. I can't fault them for that, but ACPI is as common as TCPIP now and this is one area where Linux has fallen way behind the curve. Having only some hardware work and only certain functions available just isn't good enough.
If you wanna get rich, you know that payback is a bitch
Try bitching to someone who _might_ care; e.g. your laptop vendor! Get them to fix their BIOS; broken DSDT tables are the root of most Linux ACPI woes.
@lt;len.brown:intel.com>:
o ACPI update
o ACPI build fix
o linux-acpi-2.4.22.patch
What, you can't tell from these extremely descriptive release notes?
Unfortunately, for most of the world, releasing a new kernel doesn't mean much until a distro releases it in a release. Why? Well, there is no way to tell what the hell is in a new kernel. OK, you could search the LKML, or wait for someone else to do some legwork and post the results of it. I've said it before, and I'll say it again - whoever releases the kernel should take a few minutes and do a quick writeup of what is new in the kernel. Not "fixed bug in foo.c" but something a bit more descriptive. Is it so hard? I am not being an ingrate, but I don't get why the maintainers don't do this. Yeah, you could go with the "they're engineers, not doc people!" but who better to describe what is fixed than the people who fixed it? Are you telling me that these people are incapable of describing in a sentence or two what their fix does?
No big deal I guess, and I am sure I'll get modded down for not drooling over a new kernel. But I'll bet 90% of the people who rave about it don't know what they are compiling.
My beliefs do not require that you agree with them.
Way behind? Windows has plenty of ACPI issues of its own, from what I've seen. Not only that, but Intel has at least one full time engineer working on Linux ACPI support (IIRC). Seems to me the standard itself is either too complicated for its own good, or many manufacturers are deviating for whatever reason. Hardly a fault of Linux itself. :)
Certain big name Linux developers were very anti-ACPI and very misinformed to boot (thinking that ACPI was only power management and that APM would be supported indefinately). Thus any early attempt at getting ACPI working was greeted by flames, delaying the effort by some time.
I've thought about upgrading since I normally like to run the latest stuff (plus I'm hoping 2.6 will fix the broken SBP2 driver).
However, trying to get all my settings into this new kernel was not so easy (it was quite painful upgrading to 2.4 also). I'm running on a big laptop so I have a lot of special case hardware that had to be tweeked. Now, I've been a Linux user since the kernel was at 0.97 or so and I remember thinking how complicated all those kernel options were. Jump forward to today and damn, TOO MANY OPTIONS is all I can say. 99% of it I don't care about but I have to go through each one to make sure the kernel will work... agonizing. I wish the kernel could configure itself (a la Microsoft's "detecting and installing hardware").
Combine that with trying to get nVidia drivers that work (yes, yes, there are patches and all kinds of crap I can spend time screwing around with).
And then trying to get VMware to work on the new kernel...
And so on...
Well, let's just say I'm just sticking with 2.4 for now.
The ratio of people to cake is too big
Funny, I did the exact opposite (although I wasn't using Orinoco drivers, but the D-Link G650 ones). It took me 2 minutes to fetch from CVS, build and load the module, then everything worked like a charm. I feel like I'm sounding like a damn commercial, but with a little knowledge - just a little - Linux is very rewarding. Never mind the trolls bitching about different distros, window managers and all that. Chose what you like and go with that. Help each other out once in a while.
It really works, and it's definitely among the best alternatives.
You must not be building or installing correctly. Perhaps the ebuild scripts are broken, or perhaps you're not using them correctly - I don't use Gentoo so I couldn't say.
It sounds like you built the kernel but didn't install it correctly, hence the not finding the preempt routine messages.
The safest way to recompile a kernel without problems is:
Female Prison Rape in NY
Which company would that be? Wal-Mart's the biggest employer in the world, and they have half the employees you claim to.
And from your slashblurb:
Oh, and I sneak Linux servers in the corp. all the time.
Is that how you're accelerating the deployment and installation of linux?
Do you suppose they did anything with the AIC7xxx driver?
o Aic7XXX and Aic79XX drivers
o Aic79XX and Aic7xxx Drivers
o Aic7XXX and Aic79XX Drivers
o Aic7XXX and Aic79xx Drivers
[...]
o Aic7xxx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
o Aic79xx Driver Update
o Aic7xxx Driver Update
o Aic7xxx and Aic79xx Driver Update
o Aic7xxx and Aic79xx driver Update
o Aic7xxx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
o Aic7xxx and Aic79xx Driver Update
o Aic7xxx Driver Update
o Aic79xx Driver Update
I for my own after 10 years of open source and Linux am up to search for alternatives. A commercial OS may be better (better documentation, professional development, you can make a few bucks with your work, no pain, stable ABI and API and much more).
Many of the people who are using open source are using it just for those reasons. In real life, APIs and ABIs to commercial software change rapidly because they are driven by marketing and business interests, documentation is costly and written for morons, you can't even look at the source when you are stuck, and you end up paying so much money for the privilege of using it that you won't be making any money on it.
And commercial software has the unpleasant habit of simply disappearing from the market at the most inconvenient times or having its price skyrocket unexpectedly. Remember DEC? They're gone and a lot of their software. Remember NeXT? Absorbed by Apple, and all you can get is the OS X variant; hope you didn't bet on their PC version. Remember Taligent? NeWS? Smalltalk? Microsoft Java? OS/2? Amiga? Gone, gone, gone, gone, gone, and gone.
GNU/GPL, FSF, prayer RMS they all should go to hell they are all paralyzed.
The FSF does something about software they hold the copyright to. For the Linux kernel, the kernel copyright holders need to do something. Give it a few more months--these things take time.
People stealing open source code and embedd it in closed source programs and nothing can be done against it.
Yes, that's kind of annoying, but it isn't a threat to open source software. And sooner or later, those companies tend to get into trouble anyway.