2.6.13 Linux Kernel Released
LynuxFre@k writes "Linux Torvalds announced the release of the 2.6.13 Linux kernel. He noted that there was a major change to the x86 PCI code, and that while all bugs from the change were believed to be found during the release candidate phase, it's possible that some devices may have problems. From this release on, it is intended that major changes only be merged into the kernel within two weeks after a major release. The rest of the time will be spent fixing bugs, with the goal of both increasing overall stability and decreasing the amount of time between major releases. Download the latest Linux kernel from a kernel.org mirror."
This is a cool use for the Coral Cache, mirroring files this big: the kernel.
--
Dreamhost superb hosting.
Kunowalls!!! Random sexy wallpapers (NSFW!).
Hosting 20G hd, 1Tb bw! ssh $7.95
As they say in osnews, devfs seems to have been removed from the kernel.
--
Dreamhost superb hosting.
Kunowalls!!! Random sexy wallpapers (NSFW!).
Hosting 20G hd, 1Tb bw! ssh $7.95
This PCI code rewrite doesn't bother me as much as some of the recent 2.6 releases including new drivers for obscure proprietary hardware.
A large number of organizations (as well as Debian Stable and Redhat) still use 2.4. It's pretty pathetic. 2.6 was released in December of 2003, over a year and a half ago. It offers significant performance advantages over 2.4 in many areas. Maybe instead of spending time switching policies, kernel developers should be consulting with end-users (note: this does not mean just/predominantly IBM and the other big fish. It means people like US, too) to find out why we're not using 2.6. Aside from security patches, any effort on 2.4 development/maintenance needs to stop. It's a brain drain, and active maintenance is encouraging people to be lazy in upgrading (and that's probably part of the issue).
Right now 2.6 is a lame-duck kernel, and if they keep trudging on and release the next stable without looking at why 2.6 isn't the defacto kernel of choice today, Linux will be rather fubar'd.
Please help metamoderate.
... it's GNU/Linux Torvalds!
No it's not. We're talking about the kernel.
Web Design Tips
When I can't find a stable kernel for one of my servers, it's a serious problem.
It's been hard to get long uptimes with 2.6... the network drivers are leaky/crash, SCSI support sucks.
It's just not been very hot.
I've had enough abrasive sigs. Kittens are cute and fuzzy.
There's a good summary of the new features over at LWN. Among other things, inotify has finally been merged in - about time! I wonder when Gentoo will add the new version to Portage, and if I'll dare to upgrade?
Linux DOES has a stable ABI, this is, the syscall interface. It hasn't been changed in years...I know people who is running binaries compiled for linux 1.0 in 2.6 kernels. If your app breaks or works bad when changing the kernel version (ej: openoffice when the semantics of yield() where changed in 2.5) is probably because your app was broken in first place. Now, regression and bugs can happen too, but those aren't on purpose
s /linux-2.6.git;a=blob;h=f39c9d714db3d6bf2f6440d2f6 cf9353057eeae5;hb=02b3e4e2d71b6058ec11cc01c72ac651 eb3ded2b;f=Documentation/stable_api_nonsense.txt
Maybe you mean the internal kernel API - which affects to modules, NVIDIA & friends etc. That API is unstable on purpose, as explained here: http://kernel.org/git/?p=linux/kernel/git/torvald
Or maybe you mean "compatibility" WRT gtk & friends, if GTK breaks compatibily thats their broblem
Are these crashes repeatable or do they have any kind of similarity?
I've been using Linux since 0.9x, and its been very stable for me over the years with a few exceptions that were experienced by other people as well.
My first assumption when I have a seemingly random kernel crash with no meaningful data from the OOPs or other messages is that there is a problem with my hardware.
For me, the Linux kernel is more robust than electrical power or hardware.
YMMV.
if you have a kernel that work, why upgrade? And why use the vanilla-kernels at all? Vendor-kernels are the ones that are considered stable these days. And there IS a "stable"-branch of the kernel (the 2.6.x.y).
In that case you should't be using bleeding-edge kernels, stick to the vendor-kernels. I mean, we are being conservative here?
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
When it comes to community distributions... they may handle things differently. But they can afford to... as they are the true hobbyist form of Linux. (Well, except for K/Ubuntu)
Overall, though... The astroturfing/trolling was a refreshing experience. Nice to see that you can still bring up the oldies-but-goodies (no matter how false) of linux fix-its. As a matter of fact, you should be heralded as the paragon of all members on the site. I propose a petition! Let everyone who wants to assign Mr PorchPuppy a UID of 2^32 speak now, as it is surely his proper place amongst /.ers.
I think I've said enough though. Have a nice day.
There! You're all done for another few months, or until you feel the need to upgrade again.
Dewey, what part of this looks like authorities should be involved?
You can already run X as non-root. Just don't start X at boot-up time. Then when you're computer finishes booting, login at the console, then type 'startx' and then inside of an xterm window, start up your favorite window manager. You now have X running under your username instead of root.
There is however a security risk (to you, not the system) of running X as yourself, which is described here:
http://www.gentoo.org/doc/en/fluxbox-config.xml
Read the section entitled 'Preparing X11'
lest we forget, Weta does all their video processing on massive linux clusters. I'd consider Lord of the Rings to be a pretty "professional video editing" example, wouldn't you?
filter: +3. Hey, look! all the trolls went away!