Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux Kernel 2.6.32 Released

Posted by CmdrTaco on from the download-compile-reboot-repeat dept.

diegocg writes "Linus Torvalds has officially released the version 2.6.32 of the Linux kernel. New features include virtualization memory de-duplication, a rewrite of the writeback code faster and more scalable, many important Btrfs improvements and speedups, ATI R600/R700 3D and KMS support and other graphic improvements, a CFQ low latency mode, tracing improvements including a 'perf timechart' tool that tries to be a better bootchart, soft limits in the memory controller, support for the S+Core architecture, support for Intel Moorestown and its new firmware interface, run-time power management support, and many other improvements and new drivers. See the full changelog for more details."

3 of 195 comments (clear)

  1. Re:Llacking in terminology. by Anonymous Coward · · Score: -1, Troll
    That's a really nifty idea and shows I amde the right choice in dedicating my life to Linux. I first used linux in college and was blown away by it. Pretty soon, I was delving through old unix books in the library, dreaming about fucking penguins, growing out my beard (as much as I could!) and not showering. The next logical step was a Tux tattoo. But that wasn't enough, so I had my balls cut off. When I see a new Linux release with awesome new features, I know I made the right choice. In fact, I'm considering going all the way and having my cock removed as well.

    Thanks Linus and kernel contributors!

  2. Re:One file system to rule them all by Anonymous Coward · · Score: -1, Troll

    They have a strong case of NIH-Syndrome.

    A hilarious statement coming from a Loonix turd.

  3. Re:Btrfs: kill off ext# please! by LOLLinux · · Score: 0, Troll

    But even assuming ms would use an open filesystem, they would want to alter it to make it incompatible with everyone else's implementation...

    So what? People take GPLed programs and make incompatible forks with it often. Why is it wrong if Microsoft wants to do the same with BSD code it would want to use?