Slashdot Mirror


Debian GNU/Linux 3.0 Released

emissary47 writes "The Debian Project is pleased to announce the release of Debian GNU/Linux version 3.0. Debian GNU/Linux is a free operating system, which now supports a total of eleven processor architectures, includes KDE and GNOME desktop environments, features cryptographic software, is compatible with the FHS v2.2 and supports software developed for the LSB. The Release Notes are available here."

9 of 431 comments (clear)

  1. Re:Didn't they promise to speed up release cycle? by noahm · · Score: 5, Informative
    Can any of the Debian insiders comment on what the future of Debian looks like?

    The whole point of Debian is that everything is done in the open. There's very little to be an "insider" on. Just subscribe to the mailing lists or read the archives and you'll be an insider.

    Having said that, the future of Debian looks like a blue sky, with fluffy white clouds here and there. And a little flying saucer off in the distance.

    noah

  2. Debian Released Notes by Grip3n · · Score: 4, Informative

    (because it's getting Slashdotted like mad)

    The Debian Project is pleased to announce the release of Debian GNU/Linux version 3.0. Debian GNU/Linux is a free operating system, which now supports a total of eleven processor architectures, includes KDE and GNOME desktop environments, features cryptographic software, is compatible with the FHS v2.2 and supports software developed for the LSB.

    With the addition of the IA-64 (ia64), HP PA-RISC (hppa), MIPS (mips, mipsel), and S/390 (s390) architectures, Debian GNU/Linux now supports a total of eleven architectures. It now runs on computers ranging from palmtops to supercomputers, and nearly everything in between, including the latest generation of 64 bit machines.

    This is the first version of Debian to feature cryptographic software integrated into the main distribution. OpenSSH and GNU Privacy Guard are included in the default installation, and strong encryption is now present in web browsers and web servers, databases, and so forth. Further integration of cryptographic software is planned for future releases.

    For the first time, Debian comes with the K Desktop Environment 2.2 (KDE). The GNOME desktop environment is upgraded to version 1.4, and X itself is upgraded to the much improved XFree86 4.1. With the addition of several full-featured free graphical web browsers in the form of Mozilla, Galeon, and Konqueror, Debian's desktop offerings have radically improved.

    This version of Debian supports the 2.2 and 2.4 releases of the Linux kernel. Along with better support for a greater variety of new hardware (such as USB) and significant improvements in usability and stability, the 2.4 kernel provides support for the ext3 and reiserfs journaling filesystems.

    Debian GNU/Linux 3.0 features a more streamlined and polished installation, which is translated into numerous languages. The task system has been revamped and made more flexible. The debconf tool makes configuration of the system easier and more user friendly. Debian GNU/Linux can be installed from CD, or from the network and a few floppies. It can be downloaded now, and will soon be available on CD-ROM from numerous vendors.

    Upgrades to Debian GNU/Linux 3.0 from earlier releases are automatically handled by the apt package management tool. As always, Debian GNU/Linux systems can be upgraded painlessly, in place, without any forced downtime. For detailed instructions about installing and upgrading Debian GNU/Linux, please see the release notes.

    This is the first release of Debian that is compatible with version 2.2 of the Filesystem Hierarchy Standard (FHS). Debian GNU/Linux now also supports software developed for the Linux Standard Base (LSB), though it is not yet LSB certified.

    Current Debian users may be interested to know that this release of Debian supports build dependencies, to aid in building packages from source, and apt pinning, to ease partial upgrades to our testing or unstable branch. This release of Debian features aptitude as an alternative for the venerable dselect program, which will make it easier to select packages. About four thousand new software packages were added to the distribution in Debian GNU/Linux 3.0.

    --
    To make a pun demonstrates the highest understanding of a language
  3. still-no-kde3-in-unstable by n1k0 · · Score: 5, Informative

    Add these to your sources.list and be thankful for all the good things Debian _has_ that other distributions _don't_. ;)

    deb http://kde3.geniussystems.net/debian ./
    deb-src http://kde3.geniussystems.net/debian ./

    ...and see this page for more information.

    niko

  4. Re:No forced downtime? by kenthorvath · · Score: 4, Informative

    It installs the new kernel for you first. Then you choose to boot it at your leisure. No FORCED downtime.

  5. Re:Didn't they promise to speed up release cycle? by dbarclay10 · · Score: 4, Informative

    Can any of the Debian insiders comment on what the future of Debian looks like?

    Well, there are no real "Debian insiders". However, not everybody is an active member of Debian community, so I can explain a few things in that context.

    First, before I go into what's being discussed with respect to Debian's very long release cycle, I'd just like to explain a few things.

    Debian/stable releases are typically meant for server environments, and as a stable development platform. With that in mind, where tradeoffs are made, stability is favoured over the newest software available. "Stability" doesn't just mean apps that don't crash. It also means things that don't change out from underneath you.

    System integrators, OEMs, businesses with a large base of deployed Debian machines, and developers of commercial, closed-source software all appreciate slow release cycles. A distribution which gets only critical updates over a few years is an easy distribution to target. Nothing will break for them, they can get to know the system extremely well.

    For the server environment, well-proven applications will almost always be preffered. Where a newer package is required for some feature that they wish, options ARE available.

    Debian is split into three trees. There's Debian/stable, Debian/testing, and Debian/unstable. Generally speaking, when a new package is uploaded to Debian, it first goes to "unstable" . After a suitable period of testing, and if there are no more bugs in the new package than the old package, it will be migrated to "testing". Actually, a lot more is considered, but those are probably the two most important aspects of the process.

    So, first a package is uploaded to "unstable". If it's good, it's migrated to "testing". At an arbitrary point, when things seem pretty stable, "testing" will be frozen. Developers have ample warning of this; if a version of their package in "testing" is too old for their liking, they have the opportunity to update it before the freeze.

    During the freeze, only important updates are made to packages. Security updates, updates which fix release-critical bugs, etc., etc.. When all the release-critical bugs have been fixed, the "testing" tree is made the "stable" tree, and we have a new Debian release. That's what we saw happen today :)

    Once a Debian tree has been released, only important updates are made. If Debian/stable has OpenSSH version 3.4, and there's an important security fix made in 3.5, instead of 3.5 being uploaded, the fix will be made to 3.4, and a new update to that package uploaded.

    This is all done in the interest of providing a robust, stable, easy-to-target distribution.

    The "testing" and "unstable" trees will almost always have newer versions of packages than "stable". If a user using "stable" wishes a newer package, then they can either migrate to "testing" or "unstable", or simply install the newer package and its newer dependencies. Simple as pie.

    So, really, a faster release process isn't strictly required. However, there are some very vocal parts of the Debian community which would appreciate a faster release cycle. I'm undecided on my own feelings, but there have been many, many, many suggestions.

    Basically, they all revolve around freezing "testing" earlier than has been the norm. For more information, read the list archives at http://lists.debian.org/

    For the rest of Debian's future? Package updates :) What else would be in Debian's future?
    Thanks :)

    --

    Barclay family motto:
    Aut agere aut mori.
    (Either action or death.)
  6. Re:Didn't they promise to speed up release cycle? by joib · · Score: 4, Informative

    Currently sarge == woody. Eventually newer packages will start to trickle down from sid to sarge, the same way the trickled down from sid to woody during the woody development. So yes, if you change to sarge you will be downgrading.

  7. Use the Graphical Installer for Woody! by Jagasian · · Score: 5, Informative

    You hear me! Use the beta version of the PGI ISO, the graphical user-friendly autohardware detecting installer for Woody. Check out the website here, and the ISOs are at the first link (only 100MB download for the entire ISO).

    Debian truely is the one true Linux distro. Its non-commercial, and developed by an open free internet community. Not only that, but Debian is superior to every other Linux distro. It is stable, easy to maintain, and it runs on any useful piece of computer hardware - no matter what platform that hardware is. Support Debian by simply spending the time to install and use it for your main Linux installation.

  8. Re:Outdated versions!!! Re:Debian Released Notes by Buck2 · · Score: 5, Informative

    But the stable distribution attempts to eliminate even the 0.01% of cases you have allotted due to bugs in all packages across all platforms.

    I once asked a question in #Debian.

    I asked, "Why do bugs in packages which are obviously due to the program itself [menu options crashing the program, false advertising within the documentation, totally broken config parsing, etc], get reported to the Debian package maintainers? Don't package maintainers just package stuff up and put it in the tree?"

    The response was, "A bug in a Debian package is a bug in the distribution."

    Debian stable attempts to have _all_ bugs ironed out or documented. I'm serious. This is different than RedHat [latest version] which contains an attempt to iron out a lot of bugs, but is spurred mostly by neat developments in the software they distribute. It's not good or bad either way, just different.

    You've heard it a million times, but maybe it will register one day. :) Debian has a slow release cycle. This is because they want to document and/or fix all bugs before they release things. This takes a long time. They have a slow release cycle.

    Debian unstable plus "unofficial" sources is newer than RedHat [latest version]. apt-get resolves a FUCKING SHITLOAD of dependency problems that develop using rpm.

    It's simple, really. It's nice. It makes you happy. People like Debian because it makes them feel good to just type in "apt-get install ", twiddle their thumbs for the download period, and then use it. And it almost always just works. The times that it doesn't work, it usually means that there is no such package or you spelled it wrong, and more often than not you got the name wrong.

    When this is the worst thing your distribution does, you're doing well. :)

    --

    As my father lik@(munch munch)... ....
  9. Re:Outdated versions!!! Re:Debian Released Notes by Phil+Hands · · Score: 4, Informative

    so, you want to recompile package foo, well first you need some source

    apt-get source foo

    or maybe some newer source

    apt-get source foo/unstable

    or maybe you need the source that became available 5 minutes ago, in which case you do one of the above, drop the new tarball in the current directory, go into the old Debian source directory, and run uupdate and maybe fix some patching problems in the new directory that got created for you.

    Next, you need to build this stuff, so let's get in the source directory:

    cd foo-1.2.3

    oh, but we might need some other development libraries to build this, so lets grab what we need

    apt-get build-dep foo

    that's better, now we can tweak some source or options maybe, and make ourselves a package

    debuild

    right, so now we have a new package, so we install it

    sudo dpkg -i ../foo-1.2.3*deb

    and it gets installed (or maybe it has some dependencies, if you got this far, you can work it out yourself) just like it was an official Debian package, which means you get to remove it cleanly, etc. if the need arrises.

    Who ever said source was difficult to play with in Debian? Debian is by developers, for developers -- we like source. That's why we're into Free Software.

    --

    Debian: GNU/Linux done the Linux way