Slashdot Mirror
Linux Kernel 2.6.7 Released
conrausch writes "German Heise News reports among others that the new Linux Kernel 2.6.7 was just released, and that it fixes the previously mentioned bug in the floating point exception handling. Whether or not you offer shell access to other people, get it now from kernel.org or one of the mirrors."
When are we going to see 2.4.27 with this bugfix? not all of us can afford to, or are able to switch to 2.6
I am one of many. My idea is not unique, nor do I expect my voice alone to sway you. I speak in a chorus of opinion.
Do I demonstrate my machismo via my large and increasing 2.6.6 uptime, or do I impress the chicks by running the latest kernel release?
Help!
Ydco co
Given that 2.6.x has been out for a while now, is anyone running the 2.6 series in a full blown production environment yet (say, database or web server)? If so, how does it compare to the 2.4 series?
Is going to rush to download this because it fixes probably the most destructive kernel hole in a few years. And its on slashdot.
thisnukes4u.net
I just compiled and installed it. It's not that bad.. or good... orr... how the hell should I know?
n ge Log-2.6.7
System doesn't seem to run much different, I haven't read the changelog
but for those of you who want to read the changelog it can be found HERE:
http://www.kernel.org/pub/linux/kernel/v2.6/Cha
Anyone else unable to compile with JFS enabled as module?
Google shows no hits, and it's not important enough for me to track any further at the minute (since disabling JFS is an adequate work-around for me).....
--
I'd rather have a bottle in front of me than a frontal lobotomy
Linux 2.6.7
Official GOD FAQ.
I knew if I patched and rebuilt 2.6.6 yesterday they would release 2.6.7 today :(
or are the kernel version numbers escalating rather quickly. Already at 2.6.7? Isn't the 2.4 kernel still at 2.4.2x? Can someone explain to me the reason behind the quick rise? Are they just anxious to get to v.3?
I love how everybody who asks "Why is this important?" gets modded down as a troll. This just fuels the argument that Slashdot is full of elitist pricks.
1. Post inflammatory comment calling everyone "pricks".
2. Claim martyrdom because your valid point was modded down.
3. ???
4. KARMA!
Here they go into the first round: make oldconfig.
/boot && mv arch/i386/boot/bzImage /boot/vmlinuz-2.6.7 && update-grub && reboot
Some sort slowdowns here and there but they're coming into the second round none the less: make modules modules_install bzImage.
Their CPU's are running full speed and they're almost at the finish, the excitement!
There we have it folks, 2 rounds and the AMD XP's are doing great, followed by the Intel P4's.
Now comes the most feared part for all the contestants: mv System.map
The crowd is holding its breath while the contestants approach the finish line. Owww, 1 P4 crashed with a kernel panic just before the finishline, what a shame!
The Athlon XP's crossed the finishline and were awarded with a beautifull new kernel! The Intel P4's came in second place and got the beautifull new kernel anyway!
Tune in next week for more kernel sports, when we will visit the senior compile contest between a 486sx and a 486dx
Alan needs to get to a linux hacking rehab. He still has couple of months left of his year off and I already see him in the ChangeLog!
Wait! The P4 is crying foul! Someone ran SETI@home as a background process!
tasks(723) drafts(105) languages(484) examples(29106)
If MS announced that they were releasing an update to XP this whole site would be full of posts like
...just like the ones you're getting here about Linux 2.6.7.
Namely, "are people here running their production servers with good uptime, various weird applications, exotic hardware, etc.?"
When XP SP 2 comes out, you can be damn sure people are going to ask the exact same questions about reliability, incompatibility, etc.. At MyCorp we've got staff that do nothing but stress test the latest Windows patches and releases for compatibility with our current environment. We do that because:
"Provided by the management for your protection."
Naaah, IMHO the memremap exploits were worse.
This one is 'only' a local DOS. Even if, as others say, crashed time is money, it could be much worse. At least you don't get 0wn3d, and you have a way to get back up by kicking users off, temporarily.
Drifting the topic, slightly...
This exploit, as well as the mremap ones, were derived from intimate examination of the source. So far, most of the Windows exploits have really been using 'features' for nefarious ends, not exploits of bugs. The recent Windows worms exploit a true bug in the security system, but I've heard that this one was developed from access to the source that leaked.
The Linux source has been out and discussed for over a decade, with plenty of time to find truly deep bugs. With the leak of WinNT/2k source, one hole was revealed fairly quickly. As people REALLY study that source, what else is going to emerge? (And how much code was really rewritten for XP vs reused?) Note that this isn't just a function of the source leak. As Microsoft shows more with Shared Source, more people will have the kind of access needed for this type of exploit.
The living have better things to do than to continue hating the dead.
Could someone tell me a bit about the MM patches? I've used Morton's patches for some time now but I never understood when the guts of his patches made it into an actual vanilla kernel release. Does anyone know? For example the last MM patch as of right now is for 2.6.7-rc3. Does that mean the vanilla 2.6.7 now contains all of MM before that? I never have quite understood that.
-mm patches are patches to the kernel source by a guy named Andrew Morton. Basically, his patches are more of a "testing ground" for new features that, while useful to some, may be not up to the point of risking including them into a production kernel that is used by businesses who need stable kernels. The features are therefore put into Morton's patches so they can be tested by people who want to take the risk, and some of these patches may eventually migrate to the standard kernel after testing.
Want Slashdot headlines on your site? Try SlashHead
I just thought I would post a brief message about supermount. If anyone wants to upgrade to 2.6.7 and still use supermount, I don't think vanilla kernels have it in there (yet, I'm sure it'll get in there sooner or later). I'm pretty sure the Mandrake and Gentoo kernels have support for it (gentoo-dev-sources do, anyway), but I just looked at gentoo-dev-sources and it is at version 2.6.5, dunno about Mandrake, but I'm sure it will take a few days for all the distros to catch up.
If you want to upgrade for security reasons, but you also want supermount in your kernel (as I do), this guy seems to have a patch for 2.6.7, which might come in handy if you don't want to wait for your distro to catch up. I am going to use this patch myself, but I cannot guarantee that it won't bone your system so to speak. The patch is not just supermount, it looks like it has some other stuff in it too, so decide for yourself!
Seeing as how I'm posting this, I may as well give a little background for those not "in the know". Supermount is a sort of filesystem, you mount your CD-ROM and floppy drives (or even USB sticks) with it, and it will automatically mount and unmount the media when you insert or remove it, kind of like on Windows. Personally, I think it is great, and it is hard to live without it now I have it.
You can learn more about it at the project website. Jeez, if it turns out the vanilla kernel does have supermount after all, I am going to look a right idiot... *presses Submit*