Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux 2.6.39 Released

Posted by timothy on from the domo-arigato dept.

Rainmaker2006 writes "The latest iteration of Linux kernel is out. The kernel 2.6.39 is listed in kernel.org, ready to be yours!" Linux for Devices has a short overview of what you can expect in the newest kernel; an article at Phoronix (complete with obnoxious pop-out advertising) points out a few bugs, as well.

9 of 76 comments (clear)

  1. About that Phoronix article... by SheeEttin · · Score: 5, Informative

    And for those of you who would like to actually see the Phoronix article mentioned in the summary, it's here

    (Yes, there are obnoxious ads, but only if you turn off your ad blocker and Flash blocker and mouse over the double-underlined blue words.)

  2. New acronym needed by LighterShadeOfBlack · · Score: 4, Insightful

    I really wish they wouldn't refer to Direct Rendering Manager as DRM. I know it's clear that it isn't that DRM but those letters are forever tainted, it's distracting.

    --
    Spelling mistakes, grammatical errors, and stupid comments are intentional.
    1. Re:New acronym needed by Skarecrow77 · · Score: 3, Informative

      A company I used to work for decided to use the initials "AOL" to refer internally their online product. seriously. I'm pretty sure they still do. I'm amazed that nobody ever pointed out to them that those initials were pretty much already spoken for, especially as an online product.

      Names stick. Say what you will, once a name is taken, it is taken, and you can't appropriate it unless you are pretty much in a completely different business (e.g. Apple computers vs Apple records, and that didn't blow up for a good 30 years!).

      Hell, if you want an example of name longevity, "whammy bars" on guitars are still called "tremolo bars" by most guitarists even though it is more specifically producing a vibrato effect, not a tremolo effect. Some early guitarists couldn't tell the difference, and the name stuck.

    2. Re:New acronym needed by causality · · Score: 4, Funny

      Direct Rendering Manager seems to be a more straightforward (and therefore honest) use of language than Digital Rights Management; so, it is the latter that really ought to change.

      Michael Bolton: "Why should I have to change my name? He's the one who sucks!"

      --
      It is a miracle that curiosity survives formal education. - Einstein
    3. Re:New acronym needed by shutdown+-p+now · · Score: 3, Funny

      You don't get it. This way you can sell Linux to big business, because if they ask if it has DRM, you can answer "it doesn't just have it, it's right in the kernel!"

  3. Major power consumption: an overlooked issue by feranick · · Score: 5, Interesting

    Considering how vocal Linus has been in some very technical issues in the past, I am appalled to see how underplayed the power consumption issue has been. It's a *major* issue, 30% more power consumption is a deal breaker for many users. And instead, what do we see from the kernel list: Nothing. The regressions that lead to these came in since kernel 2.6.38, and they went by in 39. At this point, I seriously doubt about the QA going on at kernel level. For example do they keep track of these kind of regressions in first place? It seems that Phoronix is doing the admirable job, but it seems it's going completely unheard. I am hopeful that 2.6.40 will fix this mess.

    1. Re:Major power consumption: an overlooked issue by nukem996 · · Score: 4, Interesting

      The bug will be fixed but its a very very complicated bug. All that is known is that somewhere between 2.6.37 and 2.6.38 some patch or patches caused the kernel to increase machine power usage. Finding the patch or patches that caused this is very difficult and thats just finding the bug. It then has to be debugged and fixed. One bug can't be a show stopper for everything else. Just give them some time.

    2. Re:Major power consumption: an overlooked issue by feranick · · Score: 3, Insightful

      Well, I will give them time. The point though remains: For the user this is a major step back, that should be a game stopper. The bug got into the system two releases back, and wouldn't be for Phoronix, it would pass unnoticed. This is what I mean by QA. Making sure that patches actually have no major regressions. If they do they should not belong to the main tree, but remain in stage until fixed. Instead, and in the meantime, the kernel evolves, and it becomes more difficult to identify, untangle and correct the regression.

    3. Re:Major power consumption: an overlooked issue by shutdown+-p+now · · Score: 3, Insightful

      One bug can't be a show stopper for everything else.

      Actually, yes, it can. It depends on the seriousness of the bug.