Slashdot Mirror
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)
It's too bad that the -lck patch is not out yet for 2.4.26.
Linux trying to match up Microsoft's security releases? +P
-------
FM Clan
And I thought I blocked his stories...
taken! (by Davidleeroth) Thanks Bingo Foo!
Never mind.
mmmhmmm, i cant wait to get my lil hanies on this one... too bad im on a lousy 56k while my ISP restructures... arrgh
Safe Journeys Space Fan, Where Ever You Are
When are they going to start using bittorrent to start distributing these things?
Two days after I upgrade to 2.6.5. Wonderful.
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
Never in a million years would I have guessed it was gay.
i've almost finished downloading all the new mandrake cd's and they're already out of date
Jesus saves souls and redeems them for valuable cash prizes
Dude, you downloaded the Mac version. You need to be sure to get linux-2.4.6.exe.
I hear he is just about ready to get the iso out...
;)
back to the drawing board I guess
MP3 Search Engine
i wish we could delete these things
Jesus saves souls and redeems them for valuable cash prizes
I've just got to say, I think Marcello's done a great job on the 2.4 series. For having to be part political leader, part CS genious, and part referee he's not given many people a reason to complain.
Damn. Maybe I should switch to Windows. Oh.. wait..
Domain name registration for $8.79 per year
879domains.co
Philippe Troin is one of many who crossed-checked the CAN list. Here are the relevant fixes in 2.4.26.
Today... around 2pm-3pm Pacific Time...
osdn.com [66.35.250.177] reports: Destination protocol unreachable.
They didn't cover the release of 2.6.5...or 2.6.4 for that matter. Why cover a 2.4 variant?
Just wondering.
"Music is everybody's possession. It's only publishers who think that people own it." - John Lennon.
i can't wait for the next one already!
Do they have a Windows installer?
WiX is open-source, it doesn't take a genius to create a launcher off Microsoft's official Windows installer.
Also, what's up with kernel usability? Didn't they read ESR? Where's a nice GUI for my Uncle Selma?
Clearly a mod hates me and makes light of my misfortune. Actually, I really don't care about a 2.4 release. Why is this /. news?
Well... in the case of my servers - I would need up go to dump the debian/stable modutils in favour of the (I believe still debian/unstable) module loader for a 2.6 kernel (can't remember which it is, but I've done it a few times upgrading desktops). This of course requires upgrading a bunch of other dependant crap.
And then there's the 3rd-party drivers. RAID controllers, etc etc. Yes, I know 2.6 is supposed to possibly figure out drivers from older kernels, but do I really want to trust that? Some of these don't have 2.6 drivers. Hell, for some they 2.4 drivers were a recent thing... I had a machine which I called the vendor to specifically get a 2.4.xx driver for a multi-modem system since the box was still running 2.2 before a hardware upgrade.
Being at the latest-and-greatest is good if it provides a noticable benefit vs the drawbacks up grading. In this case, it doesn't.
I've been putting off the seemingly arduous task of moving to 2.6.x...maybe I should just scratch my itch by upgrading to a newer 2.4.x kernel..
Straight out of the changelog:l /v2.4/Change Log-2.4.26
http://www.kernel.org/pub/linux/kerne
David Mosberger:
o ia64: Drop copyright notices on header files
Come on, this is the lamest joke I've ever heard.
Okay... This is the result of a cursory check, do your homework folks!
The R128 DRI bounds checking bug is a potential local root exploit.
According to this patch 2.4.26 contains the fix.
The isofs bug. It is locally exploitable iff you have hardware access or if you can induce someone to mount a compromised medium.
The ext3 information leak. It cannot lead to any exploit and has only the tiniest chances of giving an attacker any usable information.
The SoundBlaster Denial of Service.
But no, no mremap issues...
</KARMA>
2.4.x is important, but why the quiet on 2.6.x releases? And when is the 2.7.x tree starting? Some new features were SLOW to be added last time - even Microsoft beat Linux on IGMPv3, and that's bad!
Linux needs to be top of the heap (or stack) and to do that, development needs to be faster, with more features being added and less time spent on the politics.
Remember, you can't debug a tic. But the tic can damn near kill any project it infests.
Release Early, Release Often, Release Boldly. You don't move forwards by going back. And in this game, staying still is the same as going back.
It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
Debian users need new news too I guess.
All that lost karma!!! It should be mine!!!
Their server's BSD was dead, but paramedics were able to revive it.
CmdrTaco: You want news? /. editors. You have that luxury. You have the luxury of not knowing what I know: that this 2.4 kernel release, while tragically dull, probably saved lives. And my existence, while grotesque and incomprehensible to you, saves lives...You don't want the stuff that matters.
ScottGant: I think I'm entitled to it.
CmdrTaco: You want news?
ScottGant: I want stuff that matters!
CmdrTaco: You can't handle stuff that matters!
Son, we live in a world that has firewalls. And those firewalls have to be guarded by admins with stable kernels. Who's gonna do it? You? You, ScottGant? I have a greater responsibility than you can possibly fathom. You weep for Stanford and you curse the
We use words like integrity, dupes,stability...we use these words as the backbone to a life spent defending something. You use 'em as a punchline. I have neither the time nor the inclination to explain myself to a man who rises and sleeps under the blanket of the very security I provide, then questions the manner in which I provide it! I'd rather you just said thank you and went on your way. Otherwise, I suggest you pick up a cheap hosting company and run a website. Either way, I don't give a damn what you think you're entitled to!
I really need some sleep.
Just download once and then the patches.
while it does work in 2.6, if you need some of the esoteric features provided by patch-o-matic, your still stuck on 2.4 (if there is a patch-o-matic for 2.6, someone tell me).
Lawyers, MBA's, RIAA? A jedi fears not these things!
I changed it up a bit ... the essence is the same though.
A Few Good Admins
"Admin: You want news?"
"User: I think I'm entitled to it."
"Admin: You want news?"
"User: I want news for nerds. I want stuff that matters!"
"Admin: Son, we live in a world that has firewalls. And those firewalls have to be guarded by admins with stable kernels. Who's gonna do it? You? You, Mr. "MCSE"? I have a greater responsibility than you can possibly fathom. You weep for Microsoft and you curse Open Source. You have that luxury. You have the luxury of not knowing what I know: that this 2.6 kernel release, while tragically dull to you, probably saved lives. And my existence, while grotesque and incomprehensible to you, saves lives...You don't want the stuff that matters.
We use words like redundancy, fault tolerance, high availability, secure shells...we use these words as the backbone to a life spent defending something. You use 'em as a punchline. I have neither the time nor the inclination to explain myself to a man who logons to my Network and surfs the Internet under the blanket of the very security I provide, then questions the manner in which I provide it! I'd rather you just said thank you and went on your way. Otherwise, I suggest you pick up a stack of O'Reilly Books and build your own Network. Either way, I don't give a damn what you think you're entitled to!"
'NFS: Make sure that fsync() flushes all pending file data to disk. The current call to nfs_wb_file() will fail to flush out mmapped() dirty pages.'
I mean what the hell is this bittorrent sucks meme anyway? Have you ever used it?
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
What a day! The kernel upgrade released with DSA 479-1 was broken. Ext3 filesystems unmounable as it would appear the kernel module was missing from the initrd file (my guess, but seems logical). Quarter of an hour after I figured out that kernel-image-2.4.18-1-686_2.4.18-13_i386.deb was 1.1MB and obviously wrong I got another email from Martin Schulze announcing DSA 479-2. A quick check indicates it's a more reasonable size at 8.3MB.
:( Their updates go so smoothly normally that it's easy to become complacent and not do things with enough process.
Some egg on Debian's face today
Lessons:
1) Patch a test system first if you have access to one
2) Make sure your boot loader will boot from the old kernel after upgrading
3) Have a boot disk handy
4) Debate whether you can wait a few days before patching or whether the security liability is too high.
See this bug. I have the same PDC20265 hardware and had constant crashes until I read this bug and downgraded to 2.4.
- JFS: Add lots of missing statics and remove dead code
- JFS: Prevent hang in __lock_metapage
- JFS: Fix race in jfs_sync
Not only are those pesky hippie theives stole our precious JFS, they're also fixing bugs in it. Curse them!"
Consultancy: If you're not part of the solution, there's money to be made in prolonging the problem
Anyone know whether LVM2 got into this kernel?
Stephen
I was playing around with installing different BT clients on two computers, both of which are firewalled by a Linux box running IPCOP (http://ipcop.org). I had set up port forwarding to one of my machines behind the firewall, and tried installing BT on a different machine. When I fired up the new installation, IT ACCEPTED INCOMING CONNECTIONS! Sure, the firewall logs on the original BT machine showed a bunch of rejected packets, but the new machine heard all of them just fine and was accepting incoming connections, even though they were addressed to another IP address on that subnet.
Things that make you go "Hmmm." Sorta like Colossus and Guardian, they really wanted to be connected, didn't they.
Be who you are and say what you feel, because the people who mind don't matter, and the people who matter don't mind.
Bit Torrent is quite reliable, especially right after something new and popular appears. Just make sure that you go to kernel.org and get the MD5 checksum to compare with what your md5sum computation yields.
Be who you are and say what you feel, because the people who mind don't matter, and the people who matter don't mind.
As to point #2 if you install your kernel correctly in your /boot there is no need to overwrite previous kernels. Simply rename bzImage to something like kernel-2.x.yz and you're set.
/boot. All of them work [if I really wanted to I could boot 2.4.22 and use it just fine].
/lib/modules for all five kernels [it's 35M total btw] but I have some peace of mind that if the latest and greatest kernel is bunk I can revert trivially by rebooting ;-)
in fact I have 2.4.22 upto 2.4.26 in my
Sure I "waste" a bit of space in
Tom
Someday, I'll have a real sig.
The reason for not upgrading is that the newer the kernel, the slower the PC. If it wasn't that 2.4 provides journaling fs, I'd probably still use 2.0.38 these days. Btw, now that 2.6 is out I'm really reconsidering FreeBSD.
I have found someone who (maybe) understands ...
the Windoze-for-Internet situation: the
machine that needs the most patching for
vulnerabilities needs to be closest to the
source.
( fsck you, M$, for your
hideous online updates).
I am running OSX, Solaris, OpenBSD, Linux,
IRIX, QNX, and Netware here (besides Windoze),
so please don't judge me too harshly
For those who don't like 1000 line changelogs, here are the changes that Marcello specifically mentioned on his -pre and -rc lkml postings:
- Run Your own Linux Server on The Latest and Greatest 2.4 or 2.6 Kernel
Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?
Actually, I was thinking about this today. I work as an admin at a high school, and there's always a few students hovering about the tech crew. I get the vibe that a disproportionately high number of the geeks here are homosexual. Is this something I should know by now or just a fluke?
Does the social stigma of being gay drive otherwise normal people to geekdom? Does geekiness drive the people to alternate sexualities? Or do the two go hand-in-hand?
"Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
Welp atleast 2.6 supports a working implementation of root on nfs.
Patched all the Windows machines yesterday, fix Linux machines today. /. all week.
At least my boss can't say I've been reading
What, I thought this was a Linux kernel? Oh wait a second, that wasn't mentioned on the original post at all....
I haven't had any KFC in a while. Whatever happened to Kernel Sanders anyway?
His latest release was hacked to death, and has been end of lifed.
Oh, thanks buddy. And here I thought I had finally found Mac OS II 2.6 Amoeba. Sigh. Thanks for the correction anyway. These Slashdot articles should be more specific about what OS the kernel release is of.
Psst, any word where I can find OS I 1.0 Primordial Soup beta?
Dude, you're on wrong trail, beta releases are forward looking tech. I'm running MacOS XXX 30.1 Human already.
The isofs patch applies properly on 2.6.4. On 2.4.25, it mostly worked, but I had to add the "#include <asm/page.h>" line manually.
.ko) file into the proper place under /lib/modules, then did "rmmod isofs" and "modprobe isofs".
I had isofs compiled as a module, so I just did a "make modules" in the kernel source directory, copied the new isofs.o (or
This took about a minute on each system and didn't result in any downtime. So if you have a kernel source tree lying around with isofs as a module, it's an easy fix. And there's no need for major regression testing since only one module's affected. The R128 patch looks equally trivial, but I don't use that module. I can't find any info (or patch) for the SoundBlaster DoS, but it sounds less serious.
Honestly, I don't grasp who moderates the above as insightful.
The idiotic obsession with releasing half backed stuff in the software industry is understandable (up to a point) for companies that need to make a profit and to pay attention to the proverbial bottom line.
What is not understandable is that a project whose aim is scratching an itch, which aims to provide a tool that otherwise would not be available, would run, lemming like, in the same stupid rat race to release half backed rubish that would frustrate people involved as users and testers.
Fast development leads to more bugs, oh yes, they can be troubleshooted, but that firefighting mentality of people involved in producing software is what gives the profession and the industry a bad reputation and bad name.
I salute the Linux guys that IMNSHO are striking the right balance, in spite of the mounting commercial pressures (heck, if somebody feels Linux is not being developped fast enough they know what they can do. Hint: read the GPL).
Finally, more childish rubish: "And in this game, staying still is the same as going back". Give me a break, what about if moving forward is fallin into a 100m free fall Mr Lemming?
IANAL but write like a drunk one.
Yes you're right. It was more a reminder to be familiar with your lilo.conf (or grub.????) file and be 100% sure that you have a target for the old kernel in there. Some people fiddle with those files. Ours were good and that's what saved us, although on one of the machines the modules wouldn't load... we were lucky that was the simple machine with straight IDE and ext3 (which is of course backward compatible with ext2).
I run a home system and, until now, have always upgraded my kernel from RedHat's up2date. I have heard that Red Hat applied additional patches to the standard kernel. Could upgrading to a standard release cause problems?
That's so "OldSkool" you should be shot for that.
Bot Assisted Blogging
Not really, Linux would have to stoop down and have a realease every day and still have major vulnerabilities that go months unpatched. And if Linux releases stooped, you could never be sure if they fixed the problem.
What's the closest place for me to get my install?