Slashdot Mirror


Linux Kernel 2.6.8 Released

J ROC writes "According to The Linux Kernel Archives kernel 2.6.8 is now out. It includes some fixes from 2.6.7. Happy upgrading." You may want to read this earlier story and think twice before upgrading.

8 of 203 comments (clear)

  1. Re:2.6.8.1 by ThisNukes4u · · Score: 4, Insightful

    I guess they were really serious when they said that the stabilization of the kernel was up to the distro maintainers. Guess I won't be downloading 2.6.8 until 2.6.9 comes out.

    --
    thisnukes4u.net
  2. Summary? by tweakt · · Score: 3, Insightful

    I scanned the Changelog briefly and didn't see anything major. I usually grep for 'thinkpad' or 'laptop' (my main system), to see if there is anything nice to try out. There are some laptop_mode improvements (disk IO buffering, keeps hard drive spun down for as long as possible) which should benefit any laptop user.

    On occasion, someone will write up a nice summary of highlights. Anyone seen such a thing for 2.6.8?

  3. Re:Dam by mostlyalmighty · · Score: 3, Insightful

    I care, I bet a lot of others care too. Thus /. is serving its purpose for me.

    Upgrading your kernel is good for the soul.

  4. Re:Dual Boot? by Bloater · · Score: 2, Insightful

    The OP asked if this Linux kernel version fixes the problem, the reply was that it did not involve the kernel.

    The question is answered: No, this does not fix your bootloader. Not Grub nor Partition Magic; Neither Lilo, "the bootloader that has no name", nor any other bootloader are in any way altered by this software.

  5. Re:Download Size by Spoing · · Score: 4, Insightful
    1. I think Linux is a great kernel, but a 42 MB download is really a bit too much for my liking.

    [ suggestions for reducing the source update snipped ]

    The upgrade patch from 2.6.7 to 2.6.8 is under 4MB and can be found right along with the complete source here.

    Splitting the kernel source into parts would be a logistical problem...and I'd rather the developers not be bothered with it. If you want source, and you want small file sizes, using a diff to patch a previous release is a reasonable compromise. There are plenty of comments on the web on how to apply these patches, so being a developer isn't even necessary.

    Most of the suggestions you have would be appropriate for a binary release, though binary kernel packages are much smaller anyway so much of the benifit there is also lost.

    That said, there could be improvements on the package updates for just about every package ... I don't know any that do atomic updates (ex: MD5 sums of the files and fetch only the ones that differ...or apply a patch to make the files match.). That would be quite handy for mass deployment of files over a LAN to cut down network traffic; push out the update details to the clients, have the local systems check if they need a specific file, have the local systems report back what they need or if they are already OK. Not ideal for every situation, though it could be benificial. I wouldn't be surprised if the Tivo updates are handled like this.

    --
    A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
  6. Re:Dam by Atzanteol · · Score: 2, Insightful

    Linux updates aren't Slashdot's subject matter?

    I hate memes as much as anybody, but... Are you new here?

    --
    "Ignorance more frequently begets confidence than does knowledge"

    - Charles Darwin
  7. Re:Download Size by tjrw · · Score: 2, Insightful

    This has come up numerous times before on lkml and been debated to death. Search the archives if you want to see the arguments. Executive summary is, it isn't going to happen. If you're into kernel-hacking, or just following the latest updates, I would hope that you already have 2.6.7, in which case the patch is not particularly large. There's no need to download the whole thing every time.

  8. Re:2.6.8.1 by sloanster · · Score: 2, Insightful

    I guess they were really serious when they said that the stabilization of the kernel was up to the distro maintainers.

    LOL, the sky is not falling...

    99.9% of linux users do not build their disto from scratch, but get their distro from a vcendor, so this means absolutely nothing for the vast majority. Those that are smart enough to build their own kernels, are also smart enough to follow the kernel mailing list and apply patches.

    I've been running 2.6 kernels from kernel.org as well as -mm kernels on my FC1 boxes, which are fairly busy servers, and have had no problems. compiling 2.6.8.1 as we speak, so to speak. Also, novell/suse are shipping not only their personal and professional retail versions, but also their latest enterprise version, with the 2.6 kernel and it is rock solid.

    I agree that the 2.6 kernel is far more stable than 2.4 was at this stage -