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.

2 of 290 comments (clear)

  1. ChangeLog... by Alakaboo · · Score: 4, Insightful

    I love reading the ChangeLogs. Oftentimes they can be quite humorous:

    - David Miller: undo poll() limit braindamage

    This would have helped Bush during the election.

    - David Woodhouse: up_and_exit -> complete_and_exit

    Up and at'em, Dave!

    - me: make return value from do_try_to_free_pages() meaningful

    Do try for meaningful return values.

    - David Miller: "min()/max()" cleanups. Understands signs and sizes.

    Ouch. // min(-400, 3) == 3 // ??

    - Kevin Fleming: more disks the HPT controller doesn't like

    And you have to wonder about this one...

    - Ben LaHaise: use down_read, not down_write() in map_user_kiobuf.
    We don't change the mappings, we just read them.

  2. Re:how many kernels realeased a year? by CMiYC · · Score: 4, Insightful

    As many as needed. There are no set times or numbers. If enough little bugs are fixed, it is released. If a major bug is fixed, it is probably released sooner. In general, you only have three reasons to upgrade.

    1) The new one has fixed a bug in something you are using. Such as a new USB driver for your widget.

    2) A major security flaw is patched. Which is done way faster (and more publicily) than in most commerical settings.

    3) You enjoy cutting your teeth on new shit. Which would be a lot of us. :)

    I personally usually only upgrade if there is a dangerous remote exploit or for some functionaility. I only upgraded to 2.4.x for iptables and firewire support. Even though the backport of firewire worked fine for me.