Kernel 2.4.26 Out
StupidKatz writes "Fresh from the oven, the fine folks at kernel.org have released 2.4.26, filled with such yummy goodness as fixes for those damnable mmap() vulns, among other things. Remember to use your favorite mirror!"
← Back to Stories (view on slashdot.org)
Why do people still use the 2.4 branch? Why not move onto the 2.6 branch? Why doesn't the kernel team devote their work for the new?
ZX2C4
I don't think it's an arduous task... I thought it was going to be a big task too, until I asked on the Gentoo forums. I was told that I just need to do the usual "compile sources, update bootloader" procedure.
Or maybe that only works with Gentoo...?
Duct tape is like the Force. It has a light side, a dark side, and it holds the universe together.
What would be REALLY interesting is if the kernel source had a script triggered by something like "make update" that downloaded and installed the diff.
Lex orandi, lex credendi.
Anyone know whether LVM2 got into this kernel?
Stephen
Already done, in Gentoo.
:)
"emerge -u gentoo-sources" will fetch the current stable release and install it. The only thing left to do it the usual "make dep && make clean bzImage modules modules_install". Now, replace "gentoo-sources" with the sources set you prefer (mm, grsec, development (2.6), gaming, vanilla, etc.)
But sure, if it was implemented at kernel level, it would be easier for non-gentoo users to update to next stable release. Could be made as a modules I guess. Love/Cox/Tosatti, I hope you read this.
All Hail Discordia. Hail Eris. Fnord.
...except that gentoo doesn't use a diff at all from version to version (at least not kernel version, patch level is something diffrent). Every kernel source build in the portage tree downloads a FULL source tarball (linux-2.4.26.tar.bz2) and then patches that. 2.4.27 comes out tomarrow? You're downloading another 30M tarball (or whatever they're running nowadays).
I don't mean to rag on portage, it's a great system. It certaintly doesn't use diffs as the grandparent mentioned, though.
// Dumps core here
I am not a C guru, but that is not a vulnerability as far as I know. Just a regular bug which might be nasty in some circumstances when one uses async NFS. I for one hope that those mmap() vulnerabilities have been fixed properly in the last few releases.
The world doesn't need you.
Already saw ketchup?
http://www.selenic.com/ketchup/ketchup-0.5 :
ketchup is a script that automatically patches between kernel
versions, downloading and caching patches as needed, and automatically
determining the latest versions of several trees. Example usage:
$ ketchup 2.6-mm
2.6.3-rc1-mm1 -> 2.6.5-mm4
Applying 2.6.3-rc1-mm1.bz2 -R
Applying patch-2.6.3-rc1.bz2 -R
Applying patch-2.6.3.bz2
Applying patch-2.6.4.bz2
Applying patch-2.6.5.bz2
Downloading 2.6.5-mm4.bz2
Downloading 2.6.5-mm4.bz2.sign
Verifying signature...
gpg: Signature made Sat Apr 10 21:55:36 2004 CDT using DSA key ID 517D0F0E gpg: Good signature from "Linux Kernel Archives Verification Key "
gpg: aka "Linux Kernel Archives Verification Key "
owner.
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the Primary key fingerprint: C75D C40A 11D7 AF88 9981 ED5B C86B A06A 517D 0F0E
Applying 2.6.5-mm4.bz2