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."
Does the NVidia driver work with it?
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
And see if my Radeon 9800 Pro will work with my Nvidia Nforce2 chipset.
Anyone gotten Nvidia Nforce2 and Radeon 9800 Pro working with 3d Accel?
I really have another userid as well
Doesn't matter, all kernels are affected. (2.4+ anyway)
Dependency hell? =>
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 :(
Those of use still running P3-500's on old mobo's don't have very many compelling reasons to upgrade from 2.6.3.
If in doubt, don't upgrade unless you need new support for essential hardware or need to cover a security vulnerability. I leanred that after b0rking several systems trying to keep my kernel perpetually updated.
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?
It should be fixed. Give it a try!
+1 for Informative.
+1 for Interesting.
Somebody gave mod-power to teenagers?
Or is this all part of the collective psychology, the oh-so-powerful:
"we all belong to the same guilt/cult/group/$PREFERENCE_HERE so we should all think/act the same?"
Hmmmm!
Isn't that psychosis responsible for the greatest disasters in human history?
I need more coffee please...
Yam, yam, uga booga, yam, yam, yade, yade, uga booga, yam, yam, yade, yade
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!
Because it's a stupid thing to say. Slashdot has been announcing Linux kernel releases sometimes since the beginning of Slashdot. By now the only reason to complain about it is to be intentionally annoying. It's not exactly high-brow debate.
Making a Kernel isn't too hard. You find the correct image, (yep you probably want 2.6.7 ;), download the .tar.bz2 version.
To keep this short, we'll stick it in /usr/src:
1) su -
2) cd /usr/src
3) wget http://full.url.to.file.including.filename
4) tar xjvf linux-...tar.bz2
5) ln -s ./linux-2.6.7 ./linux
6) cd linux-2.6.7
7) make menuconfig
8) configure options - read the help for information about options, if necessary google around, usually it's pretty easy to find information about specific options
9) make bzImage
10) make modules
11) cd arch/i386/boot/
12) cp bzImage /boot/
13) edit /etc/grub.conf with your favorite editor, basically adding the new image, using the existing one as template.
reboot and enjoy :)
If the lamers have ftp upload ability and can execute cgi's via apache you'better have that fix in there too. I guess every single free webhost in the world with cgi's will go down in the next few days.
This is not a signature.
The question is, when will this patch show up on other distributions. People are sometimes not able to compile a vanilla kernel or a vanilla kernel can cause headache, e.g. SuSE 9.1 formats your filesystem with reiserfs and ACLs, but a vanilla kernel might not support this backported ACL feature.
Seen the kernel release from this point of view means, that the sistributions should hurry up to provide fixed kernel packages for their users.
wget http://www.kernel.org/pub/linux/kernel/v2.6/patch- 2.6.7.bz2 /usr/src /usr/src .config ../config.saved ../patch-2.6.7.bz2 | patch -p1 #(or maybe -p0) ../config.saved ./.config /boot/grub/grub.config # check it make sure it's right
cp patch-2.6.7.bz2
cd
mv linux-2.6.6 linux-2.6.7
bunzip2 patch-2.6.7.bz2
cd linux-2.6.7
cp
make mrproper
cat
make mrproper
cp
make oldconfig
make && make clean modules modules_install install
vi
reboot
Not to difficult. Could make it into a script, to bad I'm going to loose my uptime to patch the kernel, but oh well. Shit happens.
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!
The 2.6 kernels have a plethora of goodies as well as being faster than the 2.4 branch. Better hardware support, Crypto APIs (for IPsec), and in 2.6.4+ we have the beginnings of dm-crypt which is a better method of encrypting entire filesystems. I'm still yet to find a decent 2.6 distro that is good enough for both production and desktop environments though. Still too many bugs in most of the 2.6 based distros prevents me doing much. My newer hardware goes undetected, soundcard not working, SATA RAID being screwed up, webcam acting weird..... *sigh*
READY.
PRINT ""+-0
Informatus Technologicus
Wait! The P4 is crying foul! Someone ran SETI@home as a background process!
tasks(723) drafts(105) languages(484) examples(29106)
Someone told me today morning that linux has a security hole
. as p
http://www.eweek.com/article2/0,1759,1612368,00
and just see how fast things get fixed on this side of the planet !!
mindboggling
fifteen jugglers, five believers
Well, yes that is the patch if you are running x86_64.
u de/asm-i386/i387.h@1.5??nav=index.html|ChangeSet@- 7d|cset@1.1447
The 2.4 patch for i386 is here:
http://linux.bkbits.net:8080/linux-2.4/diffs/incl
I've been curious about what the -mm patches actually do. I know that they introduce some experimental stuff into the kernel, but that's about all I could get from Google about them. Do they improve preformance? Implement new features?
#include "sig.h"
No, they are modded down as troll because news of the latest kernel releases is WHAT SLASHDOT IS SUPPOSED TO BE ABOUT. If you don't like it, don't read it.
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.
Just a few comments to your build guide:
/usr/src ./linux-2.6.7 ./linux
/boot/ /etc/grub.conf
/boot/grub/menu.lst. .config aswell.
1) su -
Not neccessary at this early step, ie. not needed for compiling the kernel. Do a 'su' when you are about to install the compiled kernel&modules.
2) cd
5) ln -s
Not needed. 5) is actually discouraged by Linus. Just unpack the linux kernel sources somewhere and cd into that directory.
9) make bzImage
10) make modules
both commands are only needed for 2.4.x kernels and if you compile a kernel for the ix86 platform. If you are using 2.6.x, you should simply do a 'make'.
11) cd arch/i386/boot
12) cp bzImage
13) edit
are also only needed if you compile for the Linux/ix86 platform. 13) only applies if you are using GRUB as a bootloader on a RedHat system. BTW, GRUB's config file is usually in
You are also missing a 'make modules_install' and it might be a good idea to save your System.map and
Instead of 11-12) you might want to do a simple 'make install' (for 2.6.x kernels). Also try out 'make help'.
What should be under /usr/src/linux is a version of the kernel headers that your glibc was compiled against. Thus, you may have /usr/src/linux as the 2.6.6 headers that you built glibc with, when you upgrade the kernel to 2.6.7, you just use it under /usr/src/linux-2.6.7 and leave /usr/src/linux alone.
Based on my reading, someone from Nvidia gave em some hints. Nvidia had fixed the bug in the BIOS and gave the information to the manufacturers, but only one manufacturer actually fixed their BIOS (Shuttle I think?). Since no one else was fixing it, someone from Nvidia explained what the problem was and how to figure out if a BIOS had been fixed or not, as well as information on a work around to stop things from crashing. I could be wrong on this, since I still haven't had my coffee yet and this is from memory.
So far as I know those fixes went in to 2.6.6. Unfortunately, as a result of not being able to move to 2.6.6 yet, I haven't been able to test this fix (My two primary machines have NForce2 chipsets), but supposedly it's fixed.
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*
Ask her, I will bet uptime comes out on top (sorry) ;-)
Help fight continental drift.