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?
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?
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
I've got Fedora Core 2.
yum update kernel*
should install 2.6.7 right?
I'd much prefer to use an auto installer, I'm not ready for the full shebang yet.
Enlighten me here.
How is a full compile of the kernel done and how long would it take on a 3GHz,756RAM computer?
May the Maths Be with you!
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
Sure..."local" as in, "anyone who can install cgi scripts can do it."
Or any way a remote user can run arbitrary code (not even as root.).
tasks(723) drafts(105) languages(484) examples(29106)
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?
heh, I applied the patch, recompiled, rebooted into the new kenel, was definitely running a new kernel, and it still halted ... luckily I only give out shells on my ppc machine :D
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.
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
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.
This embarrassing FP exception hole has been around since 2.4. Yet I still expect to hear how much the "many eyes" of Open Source magically eradicate all bugs in all situations.
I wish it would get included in the main kernel already. It's such a desirable thing, I can't believe it hasn't made it in yet.
From the FAQ:
Q: Will supermount be included in standard kernel?
A: Frankly speaking, I do not know. Version for 2.4 kernel is still more of a hack so I would not even try to ask for it. I still do not consider 2.6 version to be ready for inclusion in mainline - although it would definitely make some things easier. If anyone thinks supermount should be part of standard kernel - feel free to ask on LKML.