Slashdot Mirror
Linux 2.6.0 Kernel Released
thenextpresident writes "It's here! Just updated on kernel.org, the Linux 2.6.0 kernel has finally arrived! We've been waiting a long time for this, and it had been rumored it was going to be released tonight. Well, it's here indeed. Happy downloading." There's also a changelog online for this long-awaited update.
[23:21] http://slashdot.org/article.pl?sid=03/12/18/041820 5&mode=nested&tid=106&tid=185&tid= 190 the sound you just heard was half a million geeks all orgasming at once!
I've been using 2.6.0-test11 for some time now, and find it quite stable and satisfactory.
Seems this fixes a few bugs, and beefs up Wireless support. Sweet. Can't wait till we start seeing this in "production systems".
This is not the sig you're looking for.
Wow, Lord of the Rings and 2.6 Kernel released on the same day? This just shows the dedication the Linux developers have. To not go see the movie and to work to release the kernel. My hats are off to these guys. They have gone above and beyond the call of duty.
Jason Lotito
Got a torrent of it for ya'll:
Linux 2.6.0 final (tar.bz2)My god. Now SCO will have to update all of their lawsuits!
At least offer a bitorrent version for those suffering the wrath of the slashdot effect.
If only the latest vanilla sources of gentoo linux were stable. I would not need to download 2.6 in order to get the nvidia opengl drivers to work.
http://saveie6.com/
I run linux as my desktop at home, and I also run it at work in a scientific computing cluster.
I'd like to know what benefits I could expect from the new kernel in each area in which I use linux.
Since it's impossible to track global downloads of the Linux 2.6.0 kernel, The SCO Group has set up a PayPal tip jar. Please abide by the honor system and send them your $699 after downloading the new kernel.
Tired of FB/Google censorship? Visit UNCENSORED!
I'm glad the new kernel is out in time for the holiday season... wait... that's sad isn't it?
Esoteric reference.
Distros like Slackware 9.1 are already 2.6 ready - meaning just plug 2.6 in and it should work! The only reason why kernel 2.6 wasn't included is, well, that it wasn't released until now :)
Peter is going to kill you, our poor server.....
X(7): A program for managing terminal windows. See also screen(1).
But I just upgraded to 2.4.21!
Redhat is on version 9 wtf?
So uh, what is new in this version?
$foo_obscure_driver doesn't work I'll never use Linux again!
Now I can finally switch from windows!
$bar_obscure_feature which I can't live without never made it in, I hate Linux.
but I *liked* make menuconfig; make clean && make modules modules_install bzimage!!
Read Dave Jones' "post-Halloween documents". You'll have to read them from backups, since the host davej's website is usually on recently suffered some sort of catastrophic hardware failure.
Thats a bit of a long list. New scheduler, pre-emption for the kernel, some new drivers, ALSA is the default for sound in this version. You can burn cd's without ide-scsi. devfs is now deprecated in favor of udev (which is roughtly the same thing but userspace as opposed to devfs's kernelspace). sysfs is also new in 2.6 which adds some information mounted in /sys. I hear firewire support is much improved as well and many other things I'm probably forgetting.
:). Now you'll have to excuse me while I reboot.
To the end user (me) 2.6 is much faster than 2.4 both in boot time and while operation. Kudos to all of the developers
This is great news! I'm excited even though I'm now an OS X dude. Once I find the time to back up my system and repartition I'll be trying LinuxPPC. Speaking of which, if anybody knows of (or wants to write) a non-destructive repartitioning tool for OS X please let me know!
-DA
For a summary of changes from 2.4 to 2.6, read Dave Jones' "post-Halloween" document. (The Changelog only lists changes from -test11 to 2.6.0 and so is not very useful. However, a full Changelog from 2.5.0 to 2.6.0 would be massive information overload, as well as just not terribly useful for a broad picture of what's different.)
http://www.kniggit.net/wwol26.html
This is a great place to start. It's very comprehensive, and a worthy read.
But if you really want a ultra-summed-up explination, 2.6 has 63.8% more kickassedness than 2.4 does. That and ALSA support built in.
$ make love
make: don't know how to make love. Stop
nvidia users might want to download the proper patches before trying out 2.6. the patches can be foundhere
the start of something?
My thesis project involves a module similar to SELinux and I have found that the best 2.6 kernel for messing around with it is actually the BK tree mantained by the Linux Security Modules (LSM) project. Technically SELinux is one module that is part of the LSM project but the two are often referred to synonymously. LSM is at: immunix and you can check out their kernel branch for extra features that are not yet in mainline 2.6 (and may not get in at all if the kernel maintainers aren't confortable with the changes)
;)
My personal project is actually a big modification of the Domain & Type enforcement that is present in LSM now. but the code is nowhere near ready for inclusion just yet
AntiFA: An abbreviation for Anti First Amendment.
Here
For those of us upgrading from 2.4 to 2.6 and don't know where to begin, you may want to check out an upgrade guide.
It's small but very helpful for someone that doesn't completely know what they're doing.
Gus
I mean I went there but there's no trusted computing logo. How can I trust software if it doesn't say I should. Linux will never be ready for the desktop until it's part of a trusted computing initiative.
You don't mirror kernel.org! They have more bandwith than God and NASA combined!
Fellowship 9/11
I'm sitting on top of a decently fast link and I'm leaving tomorrow, so I suppose this mirror couldn't hurt: linux-2.6.0.tar.bz2.
Apart from the high end SMP fixes...
On single CPU life is now more interactive.
Thread support is *much* faster and less buggy provided you have the right version of glibc.
Schedular fixes.
IDE cd burning is less CPU intensive if you dump the ide-scsi module and use the newer cdrecord instead.
and the usual driver improvements.
That's all just off the top of my head so there are probably more.
The answers is obvious:
Download & configure kernel.
Start compilation and go see Lotr with a smug "i'm more clever than thou" geek look knowing that you are actually multitasking.
Come back from the film with the kernel and modules crisply compiled for you, install boot loader and enjoy.
If not, why not? It's been 10 minutes since the kernel was posted and I'm not getting any younger.
Its great to see this go out in 2003, capping off a stellar year for open source. Mozilla 1.4/5, Gnome 2.4, KDE 3.2 (almost), Apache 2.x...and countless other pieces of the puzzle coming together in an awesome ecosystem.
Corporations haven't just 'taken notice', they are actively pushing this stuff. They are amping up great services behind the new commodity - software.
RedHat and IBM and Novell are leading the charge from the .com side while a huge developer community has taken root in the volunteer ranks.
2.6 was the icing on the cake - the version that really challenges the most established kernels across the entire spectrum. BRAVO!!
Why is an insignificant little dot-release suddenly front page "news" around here? C'mon, guys, this isn't Freshmeat.
Cheers,
IT
Power corrupts. PowerPoint corrupts absolutely.
http://minion.de/nvidia.html has patches to make the nvidia driver at the moment work on 2.6. I'm using it currently without issues.
Did I say that preempt would be working like clockwork?
No, if you install this kernel on anything but a test box, you're stoopid...You should wait till the minor releases are at least a month or 2 apart before you EVEN consider upgrading to a 2.6 kernel...or better yet, wait for Fedora Core 2 in April...
unlike 2.4 i must say 2.6 doesn't really have anything i'm very excited about...
What are you smoking? Better USB support, much better firewire support, Apple G5 and AMD Opteron support, pre-emptive kernel, ALSA by default, blah, blah blah the list goes on.
Unless you have a 386-25 with 4 megs of ram, an EGA monitor, and 40 MB MFM hard drive, you should be pretty damn excited (at least if you are a normal geek like the rest of us).
I'd rather be a conservative nutjob than a liberal with no nuts and no job.
In related news, Redhat/Fedora has announced that the next Fedora release will ship with 2.6. They've called it a "stop-ship" feature :) Fedora Core 2 is tentatively scheduled to be released in April 04.
What? Doesn't everyone?
Stop the Slashdot effect! Don't read the articles!
My preciousssssssssss...My precioussssssss 2.6...
SCOses can't haveses our precioussssssssssss kernel....
Actually it was figured out that the reported problems with preempt were really caused by user errors.
No kernel bug -> no fix needed.
do I have to send $699 to SCO if I already paid. I think this is a legitimate question that must be answered asap. I'm sure SCO will let us all know after the DDos has stopped against their network.
Look at the evidence from the Changelog:
s hing.orgh otmail.com
mdharm-usb@one-eyed-alien.net
trini@kernel.cra
jes@trained-monkey.org
James_McMechan@
Now ask yourself, do you want a patch submitted by someone at "one-eyed-alien.net" running on *your* production server? Can we really trust patches submitted by people using Hotmail accounts?
Go back to Windows, and rest assured that every developer will be using a trusted microsoft.com e-mail address. Don't you feel safer already?
You want the truthiness? You can't handle the truthiness!
From the following Cnet article:n efd_top
http://news.com.com/2100-7344_3-5127627.html?tag=
All these quotes apparently came from Mr. Morton himself.
"...the part of 2.6 that communicates with memory is less efficient, imposing a practical limit of 24GB of memory to the 32GB that 2.4 could handle. However, he believes that programmers will address the problem."
Is this reduced limit useful? Why should it be up to programmers to code around? Did I miss something?
"The new kernel also monitors for new events more frequently--1,000 times per second instead of 100--a fact that slows down the system about 1 percent..."
I assume it's to try and respond to events faster but increasing it tenfold, isn't that overkill? I mean, it slows the system down by 1% which isn't horrible and if a real-time app has a problem with it, you can always modify the kernel yourself but couldn't they have upped the polling to 250 which is a decent increase but not a 10x one.
"In addition, 2.6 requires somewhat more memory to run and shows worse performance when it has to use hard drives as extra memory under heavy loads... "
That seems reasonable that it needs a bit more memory but why should it see adverse effects under heavy loads as compared to the 2.4 kernel? Shouldn't they degrade at around the same level or are there some new file system issues that cause this?
Enlighten me.
2.4.18 works just fine for me and I see no reason to upgrade
don't all 2.4 versions before .23 have some kind of security problem?
what's your IP address? :)
It's the first I heard of it as well. Doing a quick google, there's some information about the ide-scsi issue here but it doesn't say how easy/difficult/transparent it is to set up cd-burning without it.
... but apparently there were bugs/difficulties/ideological issues involved.
I've been using ide-scsi to burn cds in 2.5 and 2.6 without any problems (and can't recall seeing any (OBSOLETE) notices beside the driver, either)
You can burn CD's in 2.4 without ide-scsi as well, using cdrecord's spiffy ATAPI interface.
"You tried your best and failed miserably. The lesson is...never try. Heh!" -Homer
Slackware 9.1 and -current still come with LVM version 1. Kernel 2.6 requires LVM2. So Slack is still not 2.6-ready, at least for people with LVM'ed filesystems. Okay, for everybody else, it is. :)
It's still a beta
But let's pretend it's finished
Linus needs testers
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
Here you go...
2
http://sco.com/OurCode/Linux/Kernel/2.4.bz2
Might just want to get the new one....
http://sco.com/ProbablyOurs/Linux/Kernel/2.6.bz
"The new kernel also monitors for new events more frequently--1,000 times per second instead of 100--a fact that slows down the system about 1 percent..."
I assume it's to try and respond to events faster but increasing it tenfold, isn't that overkill? I mean, it slows the system down by 1% which isn't horrible and if a real-time app has a problem with it, you can always modify the kernel yourself but couldn't they have upped the polling to 250 which is a decent increase but not a 10x one.
Polling 100 times a second has been the standard figure in the Linux kernel for a long long time. Meanwhile, the top CPU speed has increased by much more than one order of magnitude (say 300MHz -> 3GHz). Most desktop distributions have already been shipping with this set to 1000 already, since it makes the machine overall more responsive, something that's particularly important for a GUI.
I'm guessing that on a top-of-the line server pushing bits to this disk here, that NIC there at very high speeds, it'd be just as good as the old setting, keeping buffers flowing. That 1% quote is completely without context, and might be true on a really low-end machine where 1000 context switches takes up a lot of CPU time, but overall I don't think that's accurate.
Edit: I found this quote on a google search:
"I don't know what the costs of a higher HZ value might be, except for the obvious one: more cpu cycles will be spent servicing the timer interrupt. On my PPro, servicing the timer interrupt takes around 1500 cycles, so with HZ = 100 this accounts for fraction of a percent of the processor's time. With HZ = 1024, this still wouldn't be much more than one percent (I expect the figures to be similar for a K6)." So that figure might be accurate for a 150MHz Pentium Pro...
If you're running an embedded system or something else on limited hardware, you'd probably want to tweak that now, but then again you probably should have tweaked a lot of kernel settings in the past as well. So nothing new here, just staying with the times. Hell, on a GUI machine I'd consider experimenting with setting it even higher.
Kjella
Live today, because you never know what tomorrow brings
Linus Torvalds himself said to not use it for a couple of builds.
S W
0 .
http://linuxtoday.com/developer/2003112400826NWKN
"There is still something strange going on that seems to be triggered by preemption, so for now we suggest not enabling CONFIG_PREEMPT if you want the highest stability. On the other hand, I'd love to have more testing, so that we can try to figure out what the pattern is - but please mention explicitly that you ran with preemption if you have problems."
Someone else reported that it was just a mistake on the part of one of the testers, which was revealed http://article.gmane.org/gmane.linux.kernel/16319
Who is a troll -- a person who follows what Linus says in official annoucements, or some random person who says, "works for me" in a rude way?
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
-make xconfig looks really professional now /etc/modules.conf contains only OSS aliases, no alsa config files at all. so no sound at the moment...
-make / make modules / make modules_install has all been tidied up by the looks of it -- no more endless printout of GCC syntax. had me worried for a second that nothing was compiling but overall looks pretty slick
-alsa comes installed as default, but the configuration seems a little screwy (on debian at least) --
-usb mouse doesn't seem to work here when compiled in the kernel, but works fine as a module -- same problem i've had with 2.4.18-23
-the nvidia 2.6.0 patch available at minion.de works great, so i have a functional X11 server with nvidia modules
The only thing I can find to fault is that somehow the X11 server on the backup 2.4.23 kernel crashes on bootup due to some problem parsing the XF86Config-4 file. I'm not sure if this is a side-effect of the 2.6.0 install or something else (maybe some apt-get update X11 changes i missed?), and i've had the occasional problem before with older kernels becoming only partly functional after newer kernels are installed.
All around though, nice job! Compiling the kernel is getting easier and nicer to look at. And it seems the problems with mouse lagging during 100% CPU usage are gone, at least as far as I've tried it this evening.
Thanks to Linus and all that contributed..
experimental audiovideo minimalism: Rebuild All Your Ruins
Linus said it sucks.
1 2/ 09/1341236
In early November, Bill Davidsen
responded to a post on the LKML about a problem someone was having with burning a CD. Davidsen said:
There is a problem with ide-scsi in 2.6, and rather than fix it someone came up with a patch to cdrecord to allow that application to work properly, and perhaps "better" in some way. Since the problem with ide-scsi seems to still exist for other applications, you will probably find you have to work around the problem, by using the -pad option of cdrecord (thought that was standard now for TAO at least) or reading using the ide-cd driver.
Torvalds responded to Davidsen's post by writing:
On 6 Nov 2003, bill davidsen wrote:
>
> There is a problem with ide-scsi in 2.6, and rather than fix it someone
> came up with a patch to cdrecord to allow that application to work
> properly, and perhaps "better" in some way.
Wrong.
The "somebody" strongly felt that ide-scsi was not just ugly but _evil_, and that the syntax and usage of "cdrecord" was absolutely stupid.
That somebody was me.
ide-scsi has always been broken. You should not use it, and indeed there was never any good reason for it existing AT ALL. But because of a broken interface to cdrecord, cdrecord historically only wanted to touch SCSI devices. Ergo, a silly emulation layer that wasn't really worth it.
The fact that nobody has bothered to fix ide-scsi seems to be a result of nobody _wanting_ to really fix it.
So don't use it. Or if you do use it, send the fixes over.
Linus
The back-and-forth between Davidsen and Torvalds has continued, and as a result more and more of Torvalds disdain for the ide-scsi and cdrecord interface has bubbled to the surface. Torvalds has said, among other things, that:
* "anybody who uses cdrecord has either been confused by the silly SCSI numbering"
* "Some people ended up having to boot with ide-scsi enabled to burn CD's, but then if they wanted to watch DVD's (on the same drive), they needed to boot without it."
* "the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP!"
* "It's an interface that is based on some random hardware layout mechanism that isn't even TRUE any more, and hasn't been true for a long time."
* "It's bad from a technical standpoint (anybody who names a generic device with a flat namespace is just basically clueless), and it's bad from a usability standpoint. It has _zero_ redeeming qualities."
There's more, but that's enough to give you a sense of Torvalds' unhappiness with the whole approach of both one particular (though very popular) app and the ide-sci module itself.
http://programming.linux.com/article.pl?sid=03/
--AROS is an Open Source AmigaOS clone, and source compatible with AmigaOS! Try the x86 build at http://www.aros.org
Windows uses SCSI-emulation just like Linux 2.2 and 2.4. Using ATAPI directly is one place where Linux is way AHEAD of windows.
If you are complaining that CD-burning was not setup for you automatically (which has nothing to do with kernel 2.6), throw out your geek-friendly Gentoo, and use a user-friendly distro instead, which will setup things just like windows.
You might want to keep an eye on your 2.6.0 machine if it's on a network that's readily accessible to the outside world. Apparently not all of the security fixes that occurred in the 2.4 line have made it into 2.6.0.
Dave Jones' post halloween document, which is mentioned in an earlier post as a good summary of changes, mentions the following (near the bottom):
Security concerns.
~~~~~~~~~~~~~~~~~~
Several security issues solved in 2.4 may not yet be forward ported
to 2.6. For this reason 2.6.x kernels should not be tested on
untrusted systems. Testing known 2.4 exploits and reporting results
is useful.
It will be ready
To run Debian stable
Some time next decade
"Proudly Posting Without Reading The Article"
Does anybody have a howto on how I can migrate my LVM version 1.0.7 volumes from 2.4.23 to 2.6.0? I know LVM has been replaced by device-mapper. Do I have to run some kind of conversion tool, or will device mapper just magically find and activate my LVMs? I can't find any information on this.
Date: Thu Dec 18 2003 - 00:15:50 EST
---cut---
Desktops and laptops may have more trouble at this time because of the much wider range of hardware and because of as-yet unimplemented fixes for the hardware and BIOS bugs from which these machines tend to suffer.
During the 2.6.0 stabilization period a significant number of less serious fixes have accumulated in various auxiliary kernel trees and these shall be merged into the 2.6 stream after the 2.6.0 release. Many of these fixes appear in Andrew Morton's "-mm" tree (...)
---cut---
Should invading one's peaceful neighbours be opposed, or rewarded with trade deals?
but my point is that the quality of bugs has been pretty high lately - Linus
;)
We have bugs... but at least they are *high quality* bugs! Take that Microsoft
(Congrats to all the developers for 2.6! Looking forward to getting rid of OSS and ide-scsi!)
If both ide-cd and ide-scsi are used as a module, I don't see why you can't just load and unload the correct modules when you want to change modes.
But OTOH, why would you want to do that anyway? With ide-scsi, you can do everything you need to do with the drive, I don't see why you can't just use that mode all the time.
The biggest bonus I got from 2.6 was DMA with ATAPI commands finally works. Earlier kernels would not use DMA for ATAPI commands (read: CD/DVD burning commands) even if DMA was enabled for the IDE device. This effectively limited CD burning to the speed that PIO would work at, which was about 12x on my 900Mhz K7. It also ate up your entire CPU.
:)
With 2.6, DMA works properly with ATAPI commands, at least when using the new ATAPI virtual SCSI bus (NOT the ide-scsi module!). To use the new virtual bus, use 'dev=ATAPI:0,0,0' in a cdrecord command. You may also need to use the latest alpha of cdrecord.
I can now burn 2 CDs at once (multiple burners), at 52x without my CPU load going over 0.2!
Of course, if you had the luxury of using REAL SCSI CD burners before, this won't make a lick of difference to you.
No, it means our bandwidth-limiting isn't operating in facist mode at the moment. ISC are very understanding and usually allow us to go somewhat over limit during traffic peaks.
The actual wire is gigabit, 1000Base-SX.
-hpa
"the old cdrecord interfaces are an UNBELIEVABLE PILE OF CRAP!"
:-)
So I guess Linus just found the SCO code in linux.
2.A, you decimal supremisist
Tried these?
cpufreqd
autospeedstep
cpudyn
I'm against picketing, but I don't know how to show it.