Slashdot Log In
Linux Kernel 2.6.3 Has Been Released [updated]
Posted by
timothy
on Wed Feb 18, 2004 04:17 AM
from the shhhh dept.
from the shhhh dept.
justinarthur writes "At 04:36 UTC, Linux kernel version 2.6.3 has been made available. As is typical, downloaders are advised to utilize a mirror upon file availability. There are many changes from version 2.6.2, including recent ALSA patches, XFS fixes, and updates in many other areas." Update: 02/18 14:15 GMT by T : Peter Willis points out that kernel 2.4.25 (changelog) was also released, and writes "Incidentally, a security advisory dated today states there is an exploit in kernels up to 2.4.24 and 2.6.2, but the two releases today don't seem to reflect any changes, so get ready to patch up as soon as a patch pops up. More details on the vulnerability here."
This discussion has been archived.
No new comments can be posted.
Linux Kernel 2.6.3 Has Been Released [updated]
|
Log In/Create an Account
| Top
| 72 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
SCO's code is available for perusal (Score:5, Funny)
(http://goat.cx/ | Last Journal: Wednesday August 18 2004, @02:34PM)
Re:SCO's code is available for perusal (Score:5, Funny)
(http://www.brynmosher.com/ | Last Journal: Monday August 27, @10:15PM)
Re:SCO's code is available for perusal (Score:5, Insightful)
The full URL for the parent package is here:
http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/glibc-devel-2.2.5-213.i5 86.rpm [sco.com]
Here is the kernel mentioned in the grandparent post
http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/kernel-source-2.4.21-138 .i586.rpm [sco.com]
(as mentioned in the parents they have set up some kind of HTTP auth, but blank credentials work fine)
What is bizarre is that the files are still being updated while all this crap is going on. For example http://linuxupdate.sco.com/scolinux/update/RPMS.up dates/mc-4.5.55-719.i586.rpm [sco.com] is dated 17th Feb 2004.
Further the RPMs are cryptographically signed with GPG keys for both
SuSE Package Signing Key [9C800ACA]
Caldera Security [C4970D31]
This is proof that the files are deliberately approved and issued by Caldera/SCOX, signing packages is the most protected step that can happen in a company for its sources and binaries.
Further when I look at /usr/src/linux-2.4.21-138/COPYING I see... the GPL v2 with a note at the top by Linus as usual.
Its like the arms and legs of SCOX don't know what the 455h013 is saying. HEY IDIOTS, you're still GIVING AWAY on your websites, under the GPL, the stuff you're trying to shake down companies for!! AND ITS GPG-SIGNED BY YOU THAT IT IS OKAY!!!!
Re:SCO's code is available for perusal (Score:4, Informative)
http://linuxupdate.sco.com/scolinux/SRPMS/ [sco.com]
The thing is they are compliant to the GPL :-)
Today they put up a new web-based "buy a year's license for the SCO IP" thing on their website. But why bother when you can license any SCO IP under the GPL irrevocably and for free, from the same website? Its just madness from SCO.
Great work! (Score:5, Interesting)
(http://members.hellug.gr/iatrou/)
TODO: (Score:5, Funny)
And I don't mean having feline carnal knowledge.
Re:TODO: (Score:5, Funny)
One prog to count the lines and to the console bind them.
Gentoo disappointment... (Score:5, Interesting)
(http://douglas.mayle.org/ | Last Journal: Monday March 05 2007, @12:01PM)
I must admit to being a little disappointed right now with my Gentoo installation. I saw the article here, ran an emerge sync, and 2.6.3 is still marked as unstable. I guess I'll have to wait 15 minutes before I can install it... ;)
On a slightly related sidenote, whichever developer it was who "broke" support for the 105th key (the "Europe" key) in 2.6.1 should be drawn and quartered. It took me forever to figure out why my tilde key wasn't working. I created a text file called tilde with the character in it so that everytime I needed a tilde, I could copy and paste it... Aaarrggh
Re:Gentoo disappointment... (Score:5, Informative)
Btw, the problem was that 2.6.1 actually supported the 103rd European key, and users couldn't cope with that. Now (2.6.2+) it's treated like a regular backslash key, even though they're two different keys in reality.
Re:Gentoo disappointment... (Score:5, Interesting)
(http://douglas.mayle.org/ | Last Journal: Monday March 05 2007, @12:01PM)
Re:Gentoo disappointment... (Score:5, Funny)
You may use Windows XP, but your keyboard must be running Linux, if it's always having to run fsck.
Changes include (Score:4, Informative)
(http://iki.fi/~ptman)
network driver updates, compiler warning fixes, PPC updates, a major ALSA update and SCSI updates, NFSv4 update, XFS fixes, ARM and sparc updates
Summary Redefined by Changelog (Score:5, Insightful)
At a tidy 9472 lines, I think the word 'summary' needs a new definition...
distributions (Score:4, Interesting)
Changelogs.. (Score:5, Informative)
2.4 kernel tracking can be done here [bkbits.com]
Damn it! (Score:5, Funny)
(http://www.zealot-trivia.net/ | Last Journal: Saturday July 24 2004, @11:46PM)
I grabbed the patch, applied it, reconfigured, recompiled, and set up grub. I've been waiting and waiting but still have not suffered a single crash, so I have been unable to justify rebooting.
Is any distro already with 2.6 kernel series? (Score:5, Interesting)
(http://www.ronaldolima.eti.br/ | Last Journal: Friday January 23 2004, @04:47AM)
Re:Is any distro already with 2.6 kernel series? (Score:5, Informative)
(http://mshiltonj.com/ | Last Journal: Tuesday July 26 2005, @09:43PM)
improvements are nothing short of stunning, but I haven't tried it yet.
Re:Is any distro already with 2.6 kernel series? (Score:5, Informative)
(Last Journal: Monday November 27 2006, @04:43PM)
OTOH, even without rebuilding glibc to take advantage of the new kernel-based pthread support, I have found really nice interactivity improvements on the desktop. It's really quite nice, I wouldn't want to go back to 2.4.
Nforce fix went in (Score:5, Interesting)
Oooh, does that mean I can finally enable both APIC and ACPI support in the kernel without experiencing lockups on my Nforce2-based system? I've been waiting for quite a while for this patch to go in.
But weren't there supposed to be two (complementary) patches for this problem out there?
len.brown@intel.com
Thanks Intel guy, for allowing this AMD fix to go in.
Radeon users will be happy (Score:5, Informative)
(http://www.christopherculver.com/)
Previous kernels have never worked entirely well with my Mobile Radeon M6-P graphics card. Switching from radeon-powered X to radeonfb-powered console, or changing the resolution within radeonfb, would occasionally cause the screen to get all fuzzy, making me switch back and forth until it looked normal again.
But with the 2.6.3 kernel, there's a kickass new radeonfb driver that doesn't have any of these problems, and has improved collaboration with the BIOS to decide certain settings. No longer will peers think Linux must suck because my screen occasionally gets fuzzy.
However, I'm still only getting 435fps in glxgears with a 16MB graphics card at 1024x768 with DRI definitely on. Is this normal for a sucky notebook display card, or is there a problem with Linux's radeon gl support or my settings?
I20 drivers (Score:2)
Debian and Slackware already patched (Score:4, Insightful)
Vulnerabitily fixed in 2.6.3 and 2.4.25 (Score:5, Informative)
ACPI cure for 2.4.25 HOW-TO (Score:5, Informative)
(Last Journal: Wednesday June 21 2006, @07:17AM)
The cause is a brand new ACPI implementation which has a cutoff date of January 1st 2001. If your computer's BIOS is older than that, any ACPI support that might be present will be completely ignored by the kernel. ACPI hacker Len Brown explains that while the cutoff date is indeed arbitrary, it was already being used by certain distributions who noticed a pattern in when BIOSes with broken ACPI support where manufactured, so the ACPI hackers stuck by that concensus.
If you know for fact that ACPI worked fine on your computer until 2.4.21, you can enable it again: the cure is to put acpi=force in your bootloader configuration options.
Len also noted that there might eventually be a whitelist of older BIOS versions whose ACPI support is spotless. If you feel that your motherboard is one of those that should be whitelisted, file a bug at Kernel.org [kernel.org]. Len makes absolutely no promise whatsoever that such a whitelist will ever be implemented, but still leaves the door open for people to manifest their interest via the above bug report form.
Re:This is great (Score:1)