Slashdot Mirror


Linux Kernel 2.6.14 Released

digitalderbs writes "Linux kernel 2.6.14 was released on 10-28. OSnews reports on new features like 'HostAP, FUSE, the linux port of the plan9's 9P protocol, netlink connector, relayfs, securityfs, centrino's wireless drivers, support for DCCP (currently a RFC draft, PPTP, full 4 page-table support for ppc64, numa-aware slab allocator, lock-free descriptor lookup' and many other things. The changelog is also available."

4 of 223 comments (clear)

  1. Reiser4? by Anonymous+Cumshot · · Score: 5, Interesting

    Does anyone know if/when reiser4 will be included into the mainline kernel? I recall reading a kerneltrap interview a while back with Andrew Morton, in which he basically said "sure, why not?" to including it into the next release..

    --
    Best regards, A.C.
  2. huh? by bcrowell · · Score: 5, Interesting
    Wow, there's not a single thing on that list of features that I understand. Either these are names for things I wanted but didn't know the names for, or these are all things I don't need.

    Hasn't the kernel pretty much reached the point where, for the average user, the only problems are those that just can't be fixed -- in other words, drivers for proprietary devices that haven't had their specs released by the manufacturers?

  3. Re:Reiser4? -- victim of politics+human nature by lubricated · · Score: 4, Interesting

    If it's anything like 3 was when it came into the kernel please leave it out. 3 was only let into the kernel because reiser bitched and bitched, but it was unstable and buggy. I have been much happier with ext3.

    --
    It has been statistically shown that helmets increase the risk of head injury.
  4. Re:Reiser4? -- victim of politics+human nature by dubl-u · · Score: 5, Interesting

    and I'm not blaming Hans.

    Reading that thread, I'm not sure why. ReiserFS may be the bees' knees, but that's no excuse for that kind of behavior. Kernel style is kernel style; if Reiser thinks they should change kernel style, that's a reasonable thing to discuss, but the fuck-you-my-code's-better-than-your-crappy-code routine sure isn't the way to go about it.