Slashdot Mirror


Debian GNU/Linux 5.0 "Lenny" Released

Alexander "Tolimar" Reichle-Schmehl writes "The Debian Project is pleased to announce the official release of Debian GNU/Linux version 5.0 (codenamed Lenny) after 22 months of constant development. With 12 supported computer architectures, more than 23,000 packages built from over 12,000 source packages and 63 languages for the new graphical installer, this release sets new records, once again. Software available in 5.0 includes Linux 2.6.26, KDE 3.5.10, Gnome 2.22.2, X.Org 7.3, OpenOffice.org 2.4.1, GIMP 2.4.7, Iceweasel 3.0.6, Apache 2.2.9, Xen 3.2.1 and GCC 4.3.2. Other notable features are X autoconfiguring itself, full read-write support for NTFS, Java programs in the main repository and a single Blu-Ray disc installation media. You can get the ISOs via bittorrent. The Debian Project also wishes to announce that this release is dedicated to Thiemo Seufer, a Debian Developer who died on December 26th, 2008 in a tragic car accident. As a valuable member of the Debian Project, he will be sorely missed."

16 of 386 comments (clear)

  1. Re:A Debian release! by wahgnube · · Score: 5, Informative

    Huh?

    While it's easy to pile on with the melodrama, the last stable release, Etch, was in the middle of '07. A year and a half is an entirely reasonable amount of time to wait for an operating system release.

    I, for one, congratulate them on and thank them for their timely release!

  2. Screenshots + DPL interview by Anonymous Coward · · Score: 5, Informative

    Some first impressions on the release, screenshots and an explanation of the delay from Steve McIntyre, the Debian Project Leader, here: http://tuxradar.com/content/lenny-has-landed

  3. Re:remember by tenco · · Score: 4, Informative

    Don't do this. Squeeze won't be supported by the testing security team in the beginning: http://lists.debian.org/debian-testing-security-announce/2008/12/msg00019.html

  4. Re:A Debian release! by timmarhy · · Score: 3, Informative

    care to mention how long it took for them to get to etch?

    --
    If you mod me down, I will become more powerful than you can imagine....
  5. Re:A Debian release! by Anonymous Coward · · Score: 4, Informative
  6. Re:Best KDE 3.5 distro? by ultrabot · · Score: 4, Informative

    Now when sid starts moving again, KDE 4.2 will go in - completely avoiding the earlier, less complete releases that everybody was ranting about.

    Hopefully they will freeze KDE 4.3 with Qt 4.5. Freezing kde at 4.2 would seem like a mistake, when you consider that KDE people mostly focus on fixing bugs for 4.3. Also, Qt 4.5 should bring big performance improvements.

    --
    Save your wrists today - switch to Dvorak
  7. Re:A Debian release! by petermgreen · · Score: 5, Informative

    note: theese lengths only take account of the month not the time in the month so they may be a little off but they are good enough for the purpose

    buzz->rex 6 months
    rex->bo 6 months
    bo->hamm 13 months
    hamm->slink 8 months
    slink->potato 17 months
    potato->woody 23 months
    woody->sarge 35 months
    sarge->etch 22 months
    etch->lenny 22 months

    --
    note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
  8. Re:Blu-Ray? by sinan_imam · · Score: 4, Informative

    It is not going to be in the archives because it would waste a huge amount of space. You may build it yourself using jigdo.

  9. Re:Blu-Ray? by pabs3 · · Score: 3, Informative

    IIRC you need to use jigdo to assemble them from the packages. This page hints at that:

    http://www.debian.org/releases/lenny/debian-installer/

  10. Hardware donations by wikinerd · · Score: 4, Informative
  11. Re:Best KDE 3.5 distro? by Daengbo · · Score: 4, Informative

    I'm using Lenny right now (though Gnome), and I see both 3.5 and 4 available in Synaptic.

    We shouldn't forget the Debian Live project which has live CDs for Gnome, KDE, XFCE, and LXDE.

  12. Re:Thiemo by ColonelPanic · · Score: 3, Informative

    The word "tragic" has an actual meaning, you know. If the accident were the ineluctable consequence of a character flaw -- and I do not suggest that this be the case -- then the usage would be correct and informative.

    --
    "Skill shows through where genius wears thin." -Wittgenstein || Religion: uniting aviation and architecture.
  13. Re:release with 84 RC bugs? by tenco · · Score: 5, Informative
  14. Re:OT question ... by Helmholtz · · Score: 3, Informative

    There's nothing "grey" about the DVD solution. Using libdvdcss in the USA is a violation of the DMCA, and consequently is illegal at a federal level.

    --
    RFC2119
  15. Re:Newsworthy. Actuall news. by Anonymous Coward · · Score: 5, Informative

    Oh ffs, the OpenSSL developers were just as responsible for the snafu as Debian was. More so I'd say since the Debian developer asked on the openssl-dev list about his patch and whether anyone had any objections to it. Here's the response he got from a OpenSSL developer:http://marc.info/?l=openssl-dev&m=114652287210110&w=2/

    List: openssl-dev
    Subject: Re: Random number generator, uninitialised data and valgrind.
    From: Ulf_Möller
    Date: 2006-05-01 22:34:12
    Message-ID: 44568CE4.9020906 () openssl ! org
    [Download message RAW]

    Kurt Roeckx schrieb:
    > What I currently see as best option is to actually comment out
    > those 2 lines of code. But I have no idea what effect this
    > really has on the RNG. The only effect I see is that the pool
    > might receive less entropy. But on the other hand, I'm not even
    > sure how much entropy some unitialised data has.
    >
    Not much. If it helps with debugging, I'm in favor of removing them.
    (However the last time I checked, valgrind reported thousands of bogus
    error messages. Has that situation gotten better?)

    Got that? He was given the ok by a OpenSSL developer. They're every bit as responsible as Debian.

  16. Re:Newsworthy. Actuall news. by swillden · · Score: 3, Informative

    Got that? He was given the ok by a OpenSSL developer. They're every bit as responsible as Debian.

    Not quite. The openssl developer was right that the change didn't cause a significant problem when applied to the lines the Debian dev asked about. The Debian dev then applied the change both there and to another bit of code, and it was that second -- unreviewed -- change that did the damage.

    --
    Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.