Slashdot Mirror

← Back to Stories (view on slashdot.org)

Debian 4.0 'Etch' Released

Posted by Zonk on from the etch-up-me-harties dept.

An anonymous reader writes "Earlier today we discussed the possibility that Debian Etch might be released soon. Well, according to debian.org, it has already happened. Etch has been released: 'The Debian Project is pleased to announce the official release of Debian GNU/Linux version 4.0, codenamed etch, after 21 months of constant development. Debian GNU/Linux is a free operating system which supports a total of eleven processor architectures and includes the KDE, GNOME and Xfce desktop environments. It also features cryptographic software and compatibility with the FHS v2.3 and software developed for version 3.1 of the LSB.'"

6 of 245 comments (clear)

  1. whew!! by jackstack · · Score: -1, Troll

    Just 4 months late!! Not bad. First post!

    1. Re:whew!! by jackstack · · Score: 0, Troll

      Guess not. should have known better.

  2. YEAH!!! by __aahlyu4518 · · Score: -1, Troll

    I've heard they finally switched over to the 2.4 kernel !

  3. YOU FAIl IT? by Anonymous Coward · · Score: -1, Troll

    sure 7hat I've

  4. Debian - still alive? by diwadm · · Score: 0, Troll

    With the advent of Ubuntu, does anyone have any reason to use Debian?

  5. Re:Multipath broken in debian etch! by Anonymous Coward · · Score: -1, Troll

    you're a dumbass, you fucking noob.

    read the linux kernel mailing list. read what others are saying about this option. it's been in the kernel for 4+ years without any maintenance. it's broken and everyone knows it. the guys are like, "yeah it's broken and it's fucking up multipath. we'll get rid of it in 2.6.23 for sure"

    there's no reason why debian kernel builders should have made the conscious decision to _enable_ equal cost multipath caching. it gains you absolutely nothing, and it actually fucks up the multipath that works fine when you have it off like you should.

    again, this is something that debian conspicuously enabled that broke an already working functionality. and it that regard, debian made a mistake.