Slashdot Mirror

← Back to Stories (view on slashdot.org)

Guessing Linux 2.6.0 Release Date

Posted by timothy on from the angels-on-head-of-pin-typing dept.

thorgil writes "Guessing about the linux-2.6.0 release date is hard, but here is a new angle (pseudo-scientific): I made a graph (gif) based on errors/warnings from John Cherry's (OSDL) compile statistics for linus' linux bitkeeper tree. My guess is around 12th October, 2003. What is your guess and more important, why?"

5 of 313 comments (clear)

  1. Naaah! by Anonymous Coward · · Score: -1, Flamebait

    Don't you have better things to do with your time then plot BS stats?

    I think someone needs to take up masterbation as a hobby.

  2. Quality by slainfu · · Score: -1, Flamebait

    This is by far and away one of the crappest submissions I've seen in a long, long time. ./ needs to get some form of quality control back, pronto.

    --

    slainfu
    "I can't be a terrorist if you're sucking my bum."
  3. As long as it appears in mandrake cooker. by Anonymous Coward · · Score: -1, Flamebait

    I don't worry. Mandrake Cooker is a really under estimated "bleeding edge" distro. After all, I'm currently running 2.4.22-0.8mmdk, and its a lot better than the 2.2 kernel that shitian is using.

  4. So were you talking about Debian? by Anonymous Coward · · Score: -1, Flamebait

    Well dickhead, you can easily install a 2.4x kernel on that 'ancient' release called Woody. Do you actually read the install instructions?

    What is even better Mr Mandrake Weanie is that you can just download the latest kernel source and compile it and then install it.

    And fuck me you can even just uprade your whole release if ya want to. So much fud is spread about Debian.

  5. Re:July 13 by Anonymous Coward · · Score: -1, Flamebait

    Hell, I'd settle for a fucking working 2.4.x kernel when it comes to swsusp. I find myself booted almost exclusively to Windows XP on my laptop now because swsusp freezes on resume so many god damn times it'd make your head spin. This 'aint rocket science, people! You disable the devices, write the virtual ram to disk, and shut the fucking thing off! When it comes back up, you do the reverse. Christ, if Bill's band of fuckwads can get it working, sure as FUCK you Linux developers can. Maybe if you spent more time coding instead of sitting around Slashdot scratching your ASS, shit would actually work.

    (By the way, if you were offended by this post, that means you WERE reading Slashdot instead of coding, and therefore you have proven my point. Now get back to work, you unwashed, unkempt, unshaven, fat, smelly, disgusting, worthless piece of shit! I've got products to sell, so hurry up and write some more code that I can claim as my own.) ...Darl McBride