Slashdot Mirror
Linux Kernel 2.6.6 Released
maradong writes "The new Linux Kernel 2.6.6 has been released just 2 hours ago. The Patch from version 2.6.5 to 2.6.6, which can be downloaded on kernel.org measures 2.4MiB and the Changelog can be found at the known place."
I'm not trolling here, it is just my knowledge of Linux is limited. It seems like updates to the kernel get released all the time. How is this way of fixing bugs any different than the microsoft update? Vash
A lot of changes went in this release, and from what I read on several mailing lists, there are some regressions. For example it seems the IDE cache flush at shutdown fix is causing trouble for some people. I think I will wait for the next release...
Does anybody know if the bttv video card issue, the one that would freeze the machine when capturing from a bttv card under heavy system load, is resolved?
I'm not lazy asking about this here, it's just that I looked everywhere in the changelogs and I can't see anything about it, yet the problem is known. Perhaps the problem went away as another was fixed? Anybody has any experience on this?
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
I'm assuming it's entirely a kernel issue as cat /dev/input/mouse0 or whatever produces nothing when I play with the wheel, but it does for everything else.
[libata] Add driver for SiS 964/180 SATA.
[libata sata_sis] minor cleanups
Anyone using sis964/sata? is it working ok? any major distros you can recommend? (stuck with WinXPPro on my new machine....)
Works fine for me, straight from the source:
...
...
Module Size Used by
nvidia 2074600 12
Linux duplo 2.6.6 #1 Mon May 10 11:01:29 CEST 2004 i686 GNU/Linux
Has this been solved yet or must I keep running 2.6.3 with nforce2-apic and nforce2-disconnect-quick patches?
Apparently, the tradeoff is that your CPU runs hotter with the patches.
Granted, I know that is not the case, but 2.6.x is not even 6 months old ( 2.6.0 released December 18th, 2003) at this rate of release are we looking at 2.8 in September? This just seems crazy to me. I thought that's what the "odd" numbered kernels were for, testing. At this current rate of release it sure feels like the supposed "stable" kernels are the ones being tested on.
This isn't meant to be a troll or a flame just an observation. Many of the distros have finally gotten around 2.6, but it sure seems like the kernel devs have given the distro devs a very rapid moving target to hit. I still see all to often recomendations here and other places telling people to use 2.4x for "mission critical" use. Why?
Why is 2.6 not as reliable as 2.4 was?
Why are people in this thread commenting about all the things 2.6.6 breaks?
Why does an even kernel need to break *ANYTHING* isn't that what dev kernels are for?
I love to see progress as much as anyone, heck, I run Gentoo. I just wonder if the Kernel needs to be treated with a bit more care. Would you buy a car from an auto maker, who every month changed the engine in their car?
Introducing Microsoft Vacuum 1.0 The first Microsoft product that doesn't suck.
I just downloaded the patch and am successfully running 2.6.6. :-)
Is it me or was the boot time considerably faster than before? Almost blinked and missed it. Anyone else found that?
Now I just have to clean out init.d.
Just out of curiosity, what's it going to take to get to kernel version 3.0? Honestly, what changes, additions, etc have to be incorporated until they call it Kernel 3.0?
Damn i just love my 1.95Mb dsl line... Or would you call it a 2Mb? :)
The thing is, IMO, that we DO have a problem - we dont allways talk about the same units and sometimes it mattes!
When using MiB - NOONE (that knows what they are talking about) is in doubt what you mean - but if you say MB - noone really knows.
How kan a term that clears confusion EVER be a bad thing? The problem is people like you to insist on using terms that confuses - hopefully, in 10 years noone would be confused when you say 2MB and means 2000000B...
You're not even knowledgable enough to present your
own case, otherwise you would know that the traditional
term for 1024 bytes is "KB", not "kB". Us old farts in this
business knew that the capital K was what differed
1000 from 1024. Alas, that trick couldn't be used
for mega and giga, thus the whole system gradually
degraded over the years. Thus I have grudingly come
to accept the new MiB, KiB, GiB norms.
Absolutely. But that is essentially a third party who figures out what has been changed and writes it up. Shouldn't the providers of the kernel be able to provide that information more readily? I am not suggesting a whitepaper, or a replacement of the current changelog - just a summary supplement at a higher level. Give me the summary with the kernel. That is what I meant by being more mature. While the info at kerneltrap and other places is good, why shouldn't it come from the horse's mouth? If a third party can provide an overview, why couldn't the maintainer of the kernel do the same? They should know it well enough to be able to articulate it at the correct level of detail. There is a huge range of users between "code hackers" and "distro users". The fact that kerneltrap provides an overview is proof enough that it is needed. I just think it would be nice if it came from the source, with the source. And it doesn't have to replace what we currently get, it can just be a higher view.
I don't think it is an unreasonable suggestion. The amount of overhead it would take to create such a summary would be minimal, but I think the benefits would be well worth it.
My beliefs do not require that you agree with them.
I've heard for some time about how IBM is supporting Linux. But the 2.6.5->2.6.6 changelog really drove the point home, to me. It's amazing to see how much stevef@stevef95.austin.ibm.com has contributed, probably on IBM's nickel. :-) Keep it up, IBM.
Raj Against the Machine! http://social-butterfly.appspot.com/
The speed you get depends on the quality of the phone line. Also remember that those modems work assymetrically: the 56 kbps is only downstream. Upstream is the same speed as a 33k modem.
If anything I think the old V.34+ modems were more reliable. My old local dialup ISP used to have banks of analog lines coming into the building that were hooked up the USR V.34+ Couriers. Those babies were rock solid (even if it was a bitch to manage 450+ analog lines coming into your building). With compression enabled I could download some stuff at 8-10kB/sec. I always got 33600 baud connections and never got dropped.
Then they upgraded to digital V.90 boxes and the quality went to hell. Would typically connect at 45333 but the actual downloads were slower then downloads (compressed or not) on the V.34+ modems. The connections themselves seemed to slow down over time -- one time I downloaded a Slackware ISO -- by the end of the download the modem had slowed down to about 1kB/s. With the V.34+ modems I could push 3.5-4kB/s until hell froze over. They never had random disconnects (the V.90 bank dropped me all the time).
And don't even get me started on the upload performance of the v.90 modems. Even turning off v.90 and connecting at v.34+ speeds wouldn't help. I canceled my account and got one from the phone company -- wasn't worth paying $19.25 to have the same lousy service that I could get from the phone company for $9.95.
In my experience v.90 was nothing but marketing hype. I hated it.
I want peace on earth and goodwill toward man.
We are the United States Government! We don't do that sort of thing.
I can't believe it. After upgrading my USB Webcam didn't work anymore. I find out the pwc Driver is now removed :(
Shit, downgrade again...
You are close...
When one person says "folder" and another says "directory" the two people sometimes get confused. It's rare, but I've seen it happen.
With Linux and Windows, there is a similar confusion. Modules under Linux -- serve the same purpose and are largely in the same parts of the OS -- as drivers do under Windows.
As for Nvidia, they have installation software that is not too hard to use. It will install the NVidia kernel module for the current kernel. I'm sure you've used similar ones for Windows graphics drivers.
The kernel policies are clear, and do not cause problems for the (quick guesstimate) ~4,000 other 'drivers' bundled with the base Linux kernel. NVidia has chosen not to follow those policies so like the problematic non-WHQL Windows drivers, they can suffer similar problems.
That said, for the most part, I've been very happy with the NVidia cards I have. They were very flaky 2 years ago. Now, they work well...even with the 2.6.x kernels.
A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.