Slashdot Mirror
Linux 2.6.34 Released
diegocg writes "Linux 2.6.34 has been released. This version adds two new filesystem, the distributed filesystem Ceph and LogFS, a filesystem for flash devices. Other features are a driver for almost-native KVM network performance, the VMware balloon driver, the 'kprobes jump' optimization for dynamic probes, new perf features (the 'perf lock' tool, cross-platform analysis support), several Btrfs improvements, RCU lockdep, Generalized TTL Security Mechanism (RFC 5082) and private VLAN proxy arp (RFC 3069) support, asynchronous suspend/resume, several new drivers and many other small improvements. See the full changelog here."
Other features are a driver for almost-native KVM network performance
KVM is fantastic virtualization technology, yet Xen gets all the hype these days. Why? Paravirtualization is pretty cool stuff, but seriously, what CPU's are made without some type of hardware-assisted virtualization support?
Well, AFAIK, until veeery recently (Still beta I think) you basically have to do the same on windows. Close all apps and restart the desktop.
that this kernel already got device IDs for next years Intel hardware. This is something completely new, since Intel so far had a much more closed policy and wouldn't have told device IDs prior to the chipset release.
Now there is a really good chance that driver code will make it into the distribution kernels until the new hardware will be released for mass production. So the chances that brand new hardware will work without any flaws in 2011 are higher than ever before.
Thanks to Intel for this change in their policy. This was a small step for Intel (since everybody "knows" that they will release new chips every year) but a giant leap for providing Linux hardware compatibility right "out-of-the-box".
Because as a Linux user I have become quite accustomed to things "just working".
Unfortunately, wireless destroys that notion, causing irritation (though my thinkpad T500 shows me how it is when the stuff does work, and it's great).
Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
I used to compile kernels, but stopped. There is no way that I, as a single administrator, can perform all the necessary testing to assure that there aren't any kernel problems. So now I don't, but now I get 100% uptime instead. I prefer the uptime to the performance.
When I last used KDE years ago, that didn't work so well. For instance, my ssh connections weren't restored. And even for KDE apps the session saving thing didn't save everything.
You may ask "why should SSH connections be restored?" and I'll reply: why should my apps and connections go down in the first place just because X goes down?
Heck even in windows when I kill "explorer.exe" my apps still keep running. I know it's not the same thing, but who cares when all the fanatics keep saying Linux is so stable, but when X goes down, I lose stuff.
In my experience a cli-based Linux system may be more stable than windows XP, but X can be less stable than Windows XP SP2/SP3. I've got X to lock up or abend a fair number of times, and have had to restart X, this causes me to lose unsaved work. For a Desktop User, it matters little if the rest of the O/S is still running merrily when X goes down and takes the GUI apps along with it.
Yes I could use stuff like "screen" instead and treat X as a glorified interface to multiple screen sessions, but that's pathetic.
>ATI decided my r300-based card was legacy and discontinued it via the closed-sources drivers. I'm screwed(thankfully the open source drivers are ok but nowhere near as fast).
ATI/AMD abandoned those cards not only because they where old, but also specifically because the OSS drivers for them were complete, if not that fast. They wouldn't have dropped them otherwise.
Climate Progress - Hell and High Water