Linux Kernel 2.6.3 Has Been Released [updated] 72
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."
SCO's code is available for perusal (Score:5, Funny)
Re:SCO's code is available for perusal (Score:5, Funny)
I think I speak for everyone (Score:2)
Sometimes the sqeeky justice wheels sound just like hamster wheels.
..when I say "Squeeky wheel gets the kick! Go for the eyes Boo!"
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)
TODO: (Score:5, Funny)
And I don't mean having feline carnal knowledge.
Re:TODO: (Score:3, Informative)
Done [netsonic.fi].
Many's the time I've been guily of a when a would have done just as well...
Re:TODO: (Score:3, Insightful)
This is also a useless use of wc:
$ grep -cxP "" ChangeLog-2.6.3
1260
Re:TODO: (Score:5, Funny)
One prog to count the lines and to the console bind them.
Re:Great work! (Score:3, Informative)
Re:Great work! (Score:2)
so Linux is getting buggier as more bugs get fixed??
Re:This is great (Score:1)
Gentoo disappointment... (Score:5, Interesting)
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, Funny)
You may use Windows XP, but your keyboard must be running Linux, if it's always having to run fsck.
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)
vojtech! (Score:1)
And thanks for personally helping me customize one of the joystick drivers once-upon-a-time many moons ago.
Re:Gentoo disappointment... (Score:1)
OnTopic: I'm hoping they've fixed BTTV support, module works just fine on 2.6.0, causes a modprobe segfault and OOPS on 2.6.2 (and will kill init when compiled in
Changes include (Score:4, Informative)
network driver updates, compiler warning fixes, PPC updates, a major ALSA update and SCSI updates, NFSv4 update, XFS fixes, ARM and sparc updates
Re:Changes include (Score:2, Informative)
out-of-the-box ppc/ppc64 support, complete with G5 support (64-bit), large radeonfb driver updates, IDE oops fixes (and cleanups), and a SELinux update
Slashdot really should consider linking to kerneltrap for each kernel update that has to be reported...
Summary Redefined by Changelog (Score:5, Insightful)
At a tidy 9472 lines, I think the word 'summary' needs a new definition...
Re:Summary Redefined by Changelog (Score:2, Funny)
CJC
Re:Summary Redefined by Changelog (Score:1)
distributions (Score:4, Interesting)
Re:distributions (Score:1)
Re:distributions (Score:2, Informative)
Re:distributions (Score:3, Informative)
Re:distributions (Score:2)
If by "Debian" you mean testing/unstable, then it's already there (and has been for a while). If you mean stable, it won't be default in the next release ("sarge"), so it'll be a few more years. Either way, "scheduled for this summer" is pretty far off the mark.
Re:distributions (Score:1)
Changelogs.. (Score:5, Informative)
2.4 kernel tracking can be done here [bkbits.com]
Damn it! (Score:5, Funny)
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)
Re:Is any distro already with 2.6 kernel series? (Score:5, Informative)
improvements are nothing short of stunning, but I haven't tried it yet.
Re:Is any distro already with 2.6 kernel series? (Score:2)
FC2 will be released April 19. [redhat.com]
Re:Is any distro already with 2.6 kernel series? (Score:1)
Re:Is any distro already with 2.6 kernel series? (Score:5, Informative)
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.
Obligatory Gentoo (Score:2)
Honestly, I don't notice much of a difference, just some 'different' behavior when I'm loading the system. It's not like things compile ten times faster or mozilla opens in much less time. I noticed that my system 'loads' differently no
Re:Is any distro already with 2.6 kernel series? (Score:1)
Re:Is any distro already with 2.6 kernel series? (Score:2)
Is there already any distro with the kernel 2.6 series?
Check out the current SuSE distribution (9.0) - that came with a RC for 2.6.0. I'm not sure whether newer 2.6.x kernels have been made available via online update, as I'm not running SuSE 9.0 myself. Alternatively, the 9.1 release will probably be out in April, and I'd be very surprised if it's not based on 2.6.
-- Steve
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.
It still crashes :( (Score:3, Informative)
The lockup can be easily triggered by running "hdparm -t
I know, I know, it's easy (as well as unfair) for me to bitch and moan, since I'm not a kernel developer. But knowing that there are patches out there that could solve this problem, but still haven't made it into the kernel, it's frustrating.
For what it's worth: I haven't noticed any speed advantages between an APIC-enabled and non-APIC-enabled kern
Re:It still crashes :( (Score:1)
Yes, I've tried this too. System locked up just as you said with the 'hdparm -t /dev/hdX'.
What was fixed by this fix from the 2.6.3 kernel changlog?
[ACPI] nforce2 timer lockup from Maciej W. Rozycki
Can anyone please let me know where I can find a patch that can fix this problem properly?
Thank you
Comment removed (Score:5, Informative)
Re:Radeon users will be happy (Score:3, Interesting)
Re:Radeon users will be happy (Score:2)
70?? And video ram should have nothing to do with it, glxgears is just blasting out pixels like a machine gun. Unless Apple did some sort of magical OpenGL kung-fu to their X11 implementation, I'd say that something isn't right on your end. I rarely get less than 1000fps reported from glx gears in a big window (though that drops w
Re: (Score:1)
Re:Radeon users will be happy (Score:3, Interesting)
I've heard that glxgears is a terrible benchmark, but it piqued my curiousity enough to fire it up on my PowerBook (Radeon Mobility 9600, Mac OS X 10.3.2 w/ optional X11 installed). With the window geometry set to 1024x768 I'm getting ~1800 to ~2700 fps, it really bounces around. Given that glxgears doesn't use any texturing nor any other wizbang new features, I'm guessing that something's not r
Re:Radeon users will be happy (Score:2)
I got 20fps with software (MesaGL) rendering four years ago on a 400MHz K6-II. On any relatively recent computer, not even software rendering should be that slow.
Re:Radeon users will be happy (Score:2)
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)
Re:Vulnerabitily fixed in 2.6.3 and 2.4.25 (Score:2)
From the ChangeLog [kernel.org] of kernel-2.4.25 [kernel.org]:
Date of patch-2.4.25-pre4-pre5 (did not find pre3-pre4) ist Jan-15! Why did it take so long to get the crowd informed? Same thing happened with the other do_mremap() bug.
Hacker's guide:
ACPI cure for 2.4.25 HOW-TO (Score:5, Informative)
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.