Slashdot Mirror

← Back to Stories (view on slashdot.org)

2.4.9 Kernel Released

Posted by CmdrTaco on from the download-compile-reboot-repeat dept.

Justin writes: "Linus is off to Finland for a week or so and released 2.4.9. " Here is the Changelog for those of you interested. Yeah, it's probably gonna be a little crowded for a bit. Please post mirrors in the comments.

6 of 290 comments (clear)

  1. Stress-test it! by sulli · · Score: 2, Offtopic

    See if it responds better than Banjo...

    --

    sulli
    RTFJ.
  2. 2 compilation errors already by cyrilc · · Score: 1, Offtopic

    ...for the Alpha + i386 arch on NTFS (unistr.c) and pc_keyb.c respectively :

    personal box (AMD Duron) :

    gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall -Wstrict-prototypes -Wno-t rigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mprefe rred-stack-boundary=2 -march=i686 -malign-functions=4 -DMODULE -DMODVERSIONS -i nclude /usr/src/linux-2.4.9/include/linux/modversions.h -DNTFS_VERSION=\"1.1.16\ " -c -o unistr.o unistr.c unistr.c: In function `ntfs_collate_names': unistr.c:99: warning: implicit declaration of function `min' unistr.c:99: parse error before `unsigned' unistr.c:99: parse error before `)' unistr.c:97: warning: `c1' might be used uninitialized in this function unistr.c: At top level: unistr.c:118: parse error before `if' unistr.c:123: warning: type defaults to `int' in declaration of `c1' unistr.c:123: `name1' undeclared here (not in a function) unistr.c:123: warning: data definition has no type or storage class unistr.c:124: parse error before `if' make[3]: *** [unistr.o] Erreur 1 make[3]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs' make[2]: *** [_modsubdir_ntfs] Erreur 2 make[2]: Leaving directory `/usr/src/linux-2.4.9/fs' make[1]: *** [_mod_fs] Erreur 2 make[1]: Leaving directory `/usr/src/linux-2.4.9' make: *** [stamp-build] Erreur 2

    and on the Alpha Server 1000 :

    gcc -D__KERNEL__ -I/usr/src/kernel-source-2.4.9/include -Wall -Wstrict-prototype s -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -Wa,-mev6 -c -o pc_keyb.o pc_keyb.c In file included from pc_keyb.c:36: /usr/src/kernel-source-2.4.9/include/asm/keyboard. h:25: warning: `struct kbd_repeat' declared inside parameter list /usr/src/kernel-source-2.4.9/include/asm/keyboard. h:25: warning: its scope is on ly this definition or declaration, which is probably not what you want. pc_keyb.c:545: variable `kbdrate' has initializer but incomplete type pc_keyb.c:546: warning: excess elements in struct initializer pc_keyb.c:546: warning: (near initialization for `kbdrate') pc_keyb.c:548: warning: excess elements in struct initializer pc_keyb.c:548: warning: (near initialization for `kbdrate') pc_keyb.c: In function `parse_kbd_rate': pc_keyb.c:574: dereferencing pointer to incomplete type pc_keyb.c:575: dereferencing pointer to incomplete type pc_keyb.c:575: invalid use of undefined type `struct kbd_repeat' pc_keyb.c:576: dereferencing pointer to incomplete type pc_keyb.c:577: dereferencing pointer to incomplete type pc_keyb.c:577: invalid use of undefined type `struct kbd_repeat' pc_keyb.c:579: dereferencing pointer to incomplete type pc_keyb.c:585: dereferencing pointer to incomplete type pc_keyb.c:590: dereferencing pointer to incomplete type pc_keyb.c:591: dereferencing pointer to incomplete type pc_keyb.c: At top level: pc_keyb.c:606: conflicting types for `pckbd_rate' /usr/src/kernel-source-2.4.9/include/asm/keyboard. h:25: previous declaration of `pckbd_rate' pc_keyb.c: In function `pckbd_rate': pc_keyb.c:611: storage size of `old_rep' isn't known pc_keyb.c:612: sizeof applied to an incomplete type pc_keyb.c:614: sizeof applied to an incomplete type pc_keyb.c:615: sizeof applied to an incomplete type pc_keyb.c:611: warning: unused variable `old_rep' make[4]: *** [pc_keyb.o] Error 1 make[4]: Leaving directory `/usr/src/kernel-source-2.4.9/drivers/char' make[3]: *** [first_rule] Error 2 make[3]: Leaving directory `/usr/src/kernel-source-2.4.9/drivers/char' make[2]: *** [_subdir_char] Error 2 make[2]: Leaving directory `/usr/src/kernel-source-2.4.9/drivers' make[1]: *** [_dir_drivers] Error 2 make[1]: Leaving directory `/usr/src/kernel-source-2.4.9' make: *** [stamp-build] Error 2
  3. Re:What will the next 2.4 revision be called? by cnkeller · · Score: 1, Offtopic
    As the 2.4.x kernel series has been headed to higher and higher revision (x) numbers, I've been wondering what will occur when those numbers are exhausted. Seeing as how we're at 2.4.9, will all the next revisions be 2.4.9.x? It's probably way too early for 2.6. --Alex

    Presumably at some point, Linus will issue a freeze and we'll move on to the 2.5 devleopment series, leaving only O&M on the 2.4 line.

    --

    there are no stupid questions, but there are a lot of inquisitive idiots

  4. Dammit!!! by taliver · · Score: 1, Offtopic
    I just downloaded and burned 2.4.8 yesterday!

    Thank God I don't have disks the HPT controller desn't like.

    --

    I demand a million helicopters and a DOLLAR!

  5. Re:Who cares by Rothron+the+Wise · · Score: 1, Offtopic

    Linux isn't sick. Companies making money off it are. You're just spreading FUD, and you know it.

    --
    A witty .sig proves nothing
  6. Meaningful ChangeLog anywhere? by plaa · · Score: 1, Offtopic

    Is there any place where a meaningful ChangeLog is kept? Reading the individual changes isn't much of a help (many changes may have been made but what are their effect?). I'd like to have a place that explains the changes and tells which users should upgrade (eg. "SBLive support is much better, users with SBLives should upgrade" or the sort).

    I once tried to find a place like this, but failed. Does it exist, and if not, why not?

    --

    I doubt, therefore I may be.