Slashdot Mirror


Linux Kernel 2.6.0-test10 Released

antrix angler writes "Linus Torvalds released the 2.6.0-test10 Linux kernel today, tentatively calling it the "stoned beaver" release. Linus plans to hand the kernel over to Andrew Morton in a few weeks, and then it will be up to Andrew to decide when we see the final 2.6.0 stable kernel. Download it from a mirror."

11 of 306 comments (clear)

  1. Works For Me(TM) by fire-eyes · · Score: 2, Interesting

    It works for me. Upgraded from 2.6.0-test9-mm5.

    This may become the final 2.6.0 :)

    Rock on, Linus and team.

    --
    -- Note: If you don't agree with me, don't bother replying. I won't read it.
    1. Re:Works For Me(TM) by Anonymous Coward · · Score: 1, Interesting

      -- Note: If you don't agree with me, don't bother replying. I won't read it.

      Wow. This makes a nice refreshing change to the "If you disagree then reply or email, don't just moderate down" sigs.

      Those sigs just make too much sense and this is, afterall, slashdot. ; )

      PS, how do you know someone disagrees with you before you read their message?

  2. Honest Question by twistedcubic · · Score: 4, Interesting

    Is 2.6 really noticably faster than 2.4 for regular desktop use (X responsiveness, etc...)?

    1. Re:Honest Question by Anonymous Coward · · Score: 1, Interesting

      Yeah I'm running test9 at the moment, the responsiveness is such an improvement, whilst a process was eating up 100% cpu, all other processes in X appear like the cpu is idle. This is how computers should be.

    2. Re:Honest Question by PugMajere · · Score: 5, Interesting

      Preemption, as you describe it, has been there in every Linux kernel.

      Preemption, as Linus referred to it in the release announcement, is Kernel preemption.

      I.e, the kernel itself can be preempted. This has improved consistency for things such as xmms.

      The problems you complain about are more likely the result of the new scheduler. Tell me, what nice level does X run at on your system? If it's -10, that's why your responsiveness sucks. Stop X from being reniced to -10 from 0 and you'll find that everything performs much smoother. The new scheduler does a much better job of actually respecting priorities, and as such doesn't need adjustements such as "nice" for everyday things such as running an X server.

    3. Re:Honest Question by Stween · · Score: 2, Interesting

      No, he said for "maximum stability", it should be turned off.

      People who want preemption turned on will turn it on, and will happily live with 99% stability.

    4. Re:Honest Question by Anonymous Coward · · Score: 1, Interesting

      In my experience the new kernel scheduler is much better for games.

      Load times are sometimes cut by as much as 50% (even more in Savage) and my pings are slightly lower.

      Frames per second don't seem to be effected one way or the other. The load times and pings make a big enough difference to sell me on it. :)

  3. Udev by secondsun · · Score: 1, Interesting

    I was just wondering who here has used the new udev device loader as opposed to devfs.

    *Note: Udev is a user space program that manages device nodes by interfaceing with the kernels' hotplug functions. Devfs was a different implementation of this running in kernel land. By 2.6.0 devfs will be completly depreciated for udev.

    --
    There is nothing wrong with being gay. It's getting caught where the trouble lies.
  4. Re:Stoned Beaver? by waitigetit · · Score: 3, Interesting

    You severely overestimate the technical qualities of my boss.

    Anyway, if you want to make sure your product works on the newest kernel, you want to start testing BEFORE the stable version comes out, no?

    --
    I could care less, but not without a lobotomy
  5. Final? by fstanchina · · Score: 3, Interesting

    Now it's fun to think about it as "the final 2.6.0 stable kernel". I would rather call it the *initial* 2.6.0 stable kernel.

  6. new module stucture is great! by msh104 · · Score: 2, Interesting

    i just upgraded to 2.6-test10 and found out that insmoding the nvidia module i compiled against 2.6-test9 loads just fine! i am of course going to compile it against 2.6-test10 for maximum stability but minor kernel version driver inconsistance problems allways gave me a headache with binary only drivers. (this really inproves that)