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."
That feature is still in development. If you really need it, perhaps you should use Windows 2003 until the 2.6 kernel comes out.
For those of you who use bittorrent, try:
linux-2.4.22.tar.bz2
patch-2.4.22.bz2
Choose yer poison: Prophets or Profits
I've been running the 2.6 test for a while and the latest O1int patches from con have really made this a pleasure for desktop users. 2.6-test3-mm2 had massive skips when playing xmms and untaring, like 2.4 also has on my machine. But 2.6-test4-mm1 completely fixed this. I have not had a skip yet. Please not that this is from normal usage.
Kai Makisara:
o Change Kai Makisara's email address
I was wondering when someone would get around to this.
Absolutely! I'm not sure how to qualify it other than to say that X comes up more aggressively, it's more responsive to user input, and I haven't had any nasty spills with test3 so far.
It's probably not the smartest thing I've done running on a test kernel for my work notebook, but the added functionality including support for all of the hardware on a Sager 4760 (save the build in vid camera) makes me all warm and fuzzy inside.
It's just a shame that the Cisco VPN client isn't out for 2.6 (that I'm aware of - please correct me if I'm wrong). Otherwise I would be all set.
You are checking your backups, aren't you?
Hay, don't forget to pay us the small upgrade license fee.
IP law confuses me. I am persuaded slashdot readers who read this sig now legally owe me 699$
For the first time we have cryptographic API in a stable released version of the Linux kernel. Until recently, cryptographic software could not be exported from the U.S. without a special permission. It took some time to explain to the government that the "bad guys" already have access to strong encryption. We have succeeded. Cryptographers, rejoice!
ok here is the short:
;)
Linux = good
BSD = good
NT = bad
proprietary Unix = good but expensive
BeOS = bad
Plam = wtf is plam?
here is a comparison:
Linux VS NT = linux wins
bsd vs nt = bsd wins
anything vs NT = anything wins
bsd vs linux = linux wins
proprietary unix vs linux = linux wins but it's a tight race
bsd vs proprietary unix = bsd wins again a tight race won by price and development model
plam vs anything = again wtf is plam?
Darl, doing 24 months hard time, runs into Bubba. -- Darl, meet Bubba, he's a 350 pound homosexual dominatrix, and absolute Linux fanatic. He also admins our prison Linux machines, I mean, ADMIN'D our Linux lab. You see, once SCO started charging Linux licenses, the warden ordered Bubba to remove all Linux and only allowed him to use Microsoft products.
@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.