Slashdot Mirror

← Back to Stories (view on slashdot.org)

The Must-Fix List For 2.6.0

Posted by michael on from the quart-of-milk,-loaf-of-bread dept.

Jeremy Andrews writes "Andrew Morton posted a lengthy list of items that need to be done before the 2.5 development kernel tree should be turned into the 2.6 stable kernel tree. He prefaced his list by noting that 2.6.0 does not mean, "it's finished, ship it", alternatively offering, "I'd propose that 2.6.0 means that users can migrate from 2.4.x with a good expectation that everything which they were using in 2.4 will continue to work, and that the kernel doesn't crash, doesn't munch their data and doesn't run like a dog. Other definitions are welcome.""

1 of 45 comments (clear)

  1. 2.4 will be known as "the kernel that sucked" by Anonymous Coward · · Score: 3, Informative

    Testify, brother!

    We keep trying to go to 2.4, and end up back at good ol' 2.2 every time.

    Most of our NFS infrastructure cannot be made to run under 2.4, and the scsi drivers (especially adaptec) suck (because they are poorly rewritten 2.2 drivers) and many of the network device drivers (such as, TG3) are so poorly written they will lock up your machine completely in a packet storm. Or, alternatively, they will create a packet storm.

    I'm posting this anonymously because Alan's already mad enough at my whining and complaining.

    It's free software. Use 2.2 until something better (maybe 2.6, maybe the mythical 3.0, maybe the Hurd) evolves.