Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linux 2.4.16 Released

Posted by timothy on from the good-kernel-follows-bad dept.

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.

4 of 317 comments (clear)

  1. Linking by jeriqo · · Score: 5, Informative

    Current bandwidth utilization 96.75 Mbit/s

    Out of 100mbps..

    Linking directly to the .tar.gz from the slashdot homepage was not a good idea, timothy.

    You should have pointed to the mirrors, instead:

    --
    Alexis 'jeriqo' BRET
  2. Re:how to implement ext3 by Draoi · · Score: 5, Informative

    You need to get the latest e2fsprogs (1.22) and the latest util-linux (2.11). Don't install the
    login utils if you're installing from a source tarball instead of an rpm.

    When done, type "tune2fs -j /dev/hdwhatever". Done! A journal will be created automatically. Remember to only run this on a clean ext2 partition (make sure you're not running 2.4.15! :) ). If you're going to convert over the boot volume, make sure ext3 is built into the kernel and not a module. You shouldn't have to set any particular LILO flags (I didn't & I'm typing this
    on ext3/2.4.16pre1). Update your /etc/fstab to show the new filesystem type.

    Not sure about the Slackware stuff, but I doubt if there are any config file changes.

    Andrew Morton's EXT3 page has all the details.

    --
    Alison

    "It is a miracle that curiosity survives formal education." - Albert Einstein

  3. 2.4.16 and ALSA by pwagland · · Score: 5, Informative
    Well, this was posted for 2.4.15, but it is also relevant for 2.4.16:
    While we are talking about incompatible kernel patches, please be aware that ALSA 0.5.12 does not work under 2.4.15. You need to get the CVS version, as described here . ALSA 0.5.12 compiles, but does not work.
  4. 9 paranoia-steps for upgrading out of the bug. by aussersterne · · Score: 5, Informative

    0) Make sure you have compiled and installed a patched kernel.

    1) "shutdown now" or "init 1" as root to go single-user.

    2) sync

    3) umount all non-busy filesystems (usually only root is busy for most people).

    4) sync

    5) mount -n -o remount,ro /
    (so now the root filesystem is read-only -- this step *is* important).

    6) e2fsck -f /dev/partiton
    (once for each partition, starting with root [/] device, substitute e2fsck with reiserfsck, etc., as necessary -- force a check on each filesystem)

    7) sync, hit reset

    8) make sure not to ever boot into the buggy kernel again!

    --
    STOP . AMERICA . NOW