Slashdot Mirror


Linux 2.4.16 Released

tekniklr writes: "They just released Kernel 2.4.16. Download it here, and you can read the changelog here. This hopefully fixes the error that 2.4.15 had of corrupting filesystems on unmount." Update: 11/26 14:14 GMT by T : p.s. Don't forget to look in the mirrors.

2 of 317 comments (clear)

  1. What's the best kernel? by Griim · · Score: 5, Interesting

    I've been following all the kernel releses, and their bugs. I was just curious, what is the best way to tell which kernel is currently the most stable, without jumping immediately to the latest release? Obviously there is no way of knowing if it is, without it being out there for at least a couple of weeks.

    I was hoping that kernel.org or somewhere would list what is currently the most stable. I know that from roughly 2.4.5 through to 2.4.11 or so suffer from some sort of swapping/memory leak, I can't remember. This is just from loosely following what has been posted to slashdot in the past few weeks.

    Is there any resource tracking for this? What is the most stable of the latest kernels?

  2. So, what's the best way to upgrade? by BlueUnderwear · · Score: 4, Interesting
    Ok, say you are running 2.4.15 now. You are compiling 2.4.16. And now you want to reboot with the new kernel. But reboot implies unmount, which might trigger the bug! So what would be the safest way to jump off that 2.4.15 timebomb? Is this a situation where just pushing the reset button would be safer than a clean shutdown?

    Would remounting the filesystems read-only help? Or would that also trigger the bug?

    And, if your filesystems are reiserfs, do you need to worry too, or does this only affect the traditional filesystems.

    --
    Say no to software patents.