Slashdot Mirror


Debian 4.0 'Etch' Released

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.'"

63 of 245 comments (clear)

  1. Yay! by Compact+Dick · · Score: 5, Funny

    I still remember my Woody days *sniff*

    1. Re:Yay! by wuputah · · Score: 5, Funny

      Don't worry, you can still get a woody with etch.

      *ducks*

      Disclaimer: I am not responsible for any loss of employment or productivity by clicking on any link in this post.

      --
      Brought to you by the numbers π, e, and 0x1B.
    2. Re:Yay! by Stephen+Tennant · · Score: 2, Funny

      My first woody was a memorable experience.

      --
      I spend most of my time in bed, darling.
    3. Re:Yay! by Anonymous Coward · · Score: 2, Funny

      I hear they've got pills for that nowadays.

  2. And its not even the 1st... by arlo5724 · · Score: 5, Funny

    For a second there I thought maybe this was a late April fool's joke...

    1. Re:And its not even the 1st... by dirtyforker · · Score: 5, Funny

      Don't be silly. Debian don't release their April Fool's jokes until October.

    2. Re:And its not even the 1st... by Anonymous Coward · · Score: 5, Informative

      They did actually intend to release it on April 1st, but it got delayed ...

    3. Re:And its not even the 1st... by koxkoxkox · · Score: 5, Informative
      Parent should be modded informative and not funny, as it is true : see http://lists.debian.org/debian-devel-announce/2007 /03/msg00023.html

      Our secret plan was to announce the release on April 1st
      (that would have been fun, don't you think so :) ), but well - quality is
      more important.
  3. Multipath broken in debian etch! by ljaguar · · Score: 5, Informative

    etch ships with CONFIG_IP_ROUTE_MULTIPATH_CACHED (experimental) enabled in the kernel. This breaks the multipath route behavior in iproute. As the google search shows, it is wreaking havoc with anyone using multipath and dual-wan systems. Those who upgraded this morning to the new stable may be in for a ride. This is a known and documented issue but cannot be found in debian's bug tracking system. This issue is not unique to Debian but it should not have passed through the release engineering for the new stable release.

    1. Re:Multipath broken in debian etch! by Bitsy+Boffin · · Score: 2, Insightful

      Surely anybody doing anything like that would be rolling thier own kernel anyway? The only time I've used the Debian supplied kernels is when installing, soon as that's done I always compile a fresh one.

      --
      NZ Electronics Enthusiasts: Check out my Trade Me Listings
    2. Re:Multipath broken in debian etch! by fo0bar · · Score: 2, Interesting

      etch ships with CONFIG_IP_ROUTE_MULTIPATH_CACHED (experimental) enabled in the kernel. This breaks the multipath route behavior in iproute. As the google search shows, it is wreaking havoc with anyone using multipath and dual-wan systems. Those who upgraded this morning to the new stable may be in for a ride. This is a known and documented issue but cannot be found in debian's bug tracking system. This issue is not unique to Debian but it should not have passed through the release engineering for the new stable release.

      So, this was reported for a different kernel on a different distro? What happened when you filed the bug report with Debian's BTS?
    3. Re:Multipath broken in debian etch! by Anonymous Coward · · Score: 2, Insightful

      not everyone's got the time and rarely anyone has the need. don't be a gentoo user.

    4. Re:Multipath broken in debian etch! by ljaguar · · Score: 4, Interesting

      i didn't know about it until i updated and things broke.

      as a debian stable user, there's a reasonable expectation that, after 21 months in development, they don't ship a kernel with experimental feature that is known to be broken?

      I don't mean this is an experimental feature that breaks sometimes. This feature is just clearly documented to be broken. As in it doesn't work.

      I only found out about the stuff that I posted because I updated this morning and all hell broke loose.

      I know I should have tested it on a test machine before bringing it into production. (or maybe waited a bit) But this is a small machine in an informal setting. I don't have a test machine. But I do have 20+ users with slow internet. and it's really not asking for too much to expect a thing so blatant.

    5. Re:Multipath broken in debian etch! by cxreg · · Score: 2, Insightful

      not everyone's got the time and rarely anyone has the need. don't be a gentoo user.

      That's pretty ignorant. Few if any pieces of software have the number of compile time options as the Linux kernel. Even if you module-ize everything you possibly can, there are still many choices you make that you are bound to, such as IO schedulers and pre-empting.

      Any serious Linux user is capable of and knows the value of compiling their own kernel.

    6. Re:Multipath broken in debian etch! by cymen · · Score: 5, Insightful

      If you have no test system and the machine is providing service to users then do not upgrade to .0 releases. It's simple common sense. Maybe you had some overwhelming need to get this release that goes against the need to keep service reliable but you didn't mention it so I'll assume not. Let other people do the testing of that .0 release to find all the bugs and huge gotchas that are basically inevitable.

    7. Re:Multipath broken in debian etch! by dondelelcaro · · Score: 4, Insightful

      This is a known and documented issue but cannot be found in debian's bug tracking system. This issue is not unique to Debian but it should not have passed through the release engineering for the new stable release.

      The reason why it slipped through the release engineering for the new stable release is quite simply because no one reported it as a bug.

      If someone had reported it, it would have been dealt with and otherwise resolved. Indeed, it may still be resolved in a point release, but it definetly won't be unless you (or someone like you) who experiences the bug files a bug in the bug tracking system (using reportbug or your MUA). Since (as of a few days ago) no one has filed such a bug related in anyway to MULTIPATH_CACHED, it has not been fixed.

      Considering the sheer number of people who (supposedly) use testing, none of whom apparently found the bug and/or bothered to report it, it was just not a popular feature to have been tested properly. Like it or not, a critical part of Debian's QA are the users who are using the testing and unstable distributions and reporting bugs. If they don't find it, no one will. (In case you haven't figured it out yet, there's nothing magical about being a Debian Developer in this regard; we're users too, and do the same type of testing.)

      --
      http://www.donarmstrong.com
    8. Re:Multipath broken in debian etch! by Macka · · Score: 3, Insightful

      I know I should have tested it on a test machine before bringing it into production. (or maybe waited a bit) But this is a small machine in an informal setting. I don't have a test machine. But I do have 20+ users with slow internet. and it's really not asking for too much to expect a thing so blatant.
      Man, that's pretty reckless, and you know it. Did you even take a backup first? As for not having a test machine, with Xen and VMware are your disposal these days there's no real excuse for not installing it elsewhere, and at least taking a few days to give it the once over before going near a real server. The truth is that you rushed in without proper forethought and planning and you got burned.

    9. Re:Multipath broken in debian etch! by Anonymous Coward · · Score: 5, Insightful

      When you start with Linux, you use the stock kernel, because it is easily available and works. When you gain experience, you start to compile your own. When you become a professional sysadmin, you use the stock kernels, because they are easily available and work.

    10. Re:Multipath broken in debian etch! by ljaguar · · Score: 3, Informative

      you say that as if debian .0 releases are just any old .0 releases.

      debian testing release is one of the most popular distribution in its own right.

      this isn't exactly some hacked up job released after big push to meet deadline. this went through months of release engineering and countless beta-testers.

      debian stable release (the snapshot of etch as of today) do not get updates or bugfixes. etch 4.0 will not see any updates to gnome or kernel or gaim or anything. debian stable only gets security bugfixes. (if the bug is just a bug without security implications, it does not get fixed.)

      don't you think this puts on an extra burden of not enabling (once again, known to be nonfunctional) experimental kernel option?

      yes, testing before live production is good practice. yes, patience before upgrading is a virtue. but only because debian fucks up sometimes. if debian doesn't fuck up ever, patience is not a virtue. and i'm saying that debian fucked up.

    11. Re:Multipath broken in debian etch! by oddityfds · · Score: 2, Insightful

      > Any serious Linux user is capable of

      Yeah. Except they always seem to end up disabling initrd for some unknown reason ("initrd is hard, man..." ... not), and then forget to reenable it when they switch back!

      > and knows the value of compiling their own kernel.

      Yup. 0, to me, except if I do some forms of kernel hacking.

      The statment "Everyone serious compiles their own kernel anyway" is just not true.

    12. Re:Multipath broken in debian etch! by rbanffy · · Score: 2, Interesting

      The problem with rolling out my own kernel is that the more customized the machine gets, the more complicated it is to rebuild it.

      I had used my own kernel fresh from kernel.org for ages, but then I realized it was so much more work than just running the stock kernel - that had all the problems and workarounds documented - in order to be on the bleeding edge (something hard to do with Debian stable, anyway). I just gave up on it. I thought that if there is a package manager, I should use it fully. "linux-image" is a package.

      I see heavily customized kernel machines or hand-installed software have more maintenance problems, take longer to rebuild on disasters and, in general, cost more to keep running than fully packaged ones.

      If running stock machines increases reliability and reduces cost, it's only my sense of adventure that kept me building my own kernels. It was nice to learn my way around it and is a handy knowledge if something really requires it, but, if the standard one does the job you, I advise you to stay with it.

      That said, I still prefer to install the "non-infrastructure software" on a given machine (Zope, Plone, JDK, Tomcat, Rails are the usual suspects) by myself, outside package management. I don't want to be surprised by apt if something breaks the hard way.

    13. Re:Multipath broken in debian etch! by daveewart · · Score: 4, Insightful

      Any serious Linux user is capable of and knows the value of compiling their own kernel.

      Which includes knowing when it is not necessary to do so. Unless you have extremely strange hardware, or very esoteric requirements for the system, the packaged kernels are absolutely fine. Building your own gains very little over the packaged kernels in these circumstances, either in performance or convenience; it will probably actually make life more complicated, as you will need to keep your kernel up-to-date manually, rather than just using the newer packaged kernel for your distro.

      --
      "If you think the problem is bad now, just wait until we've solved it." --- Arthur Kasspe
    14. Re:Multipath broken in debian etch! by GrenDel+Fuego · · Score: 3, Insightful

      I think at the end of the day it all depends on what you need to support. If you're supporting a single high performance system, well then a hand optimized kernel makes sense.

      If you're supporting a few hundred servers then any differences between the systems need to be kept to a minimum.

    15. Re:Multipath broken in debian etch! by fimbulvetr · · Score: 2, Insightful

      I think you're trolling, you can count the number of servers you admin on one hand, or you're inexperienced. You might say it's because I'm a lazy slob, I might say it's because I have several hundred machines. While groups of them are the same (6 here, 12 there, etc.), it'd be absurd to even consider what you're suggesting - not to mention the insanity a security update could bring.

    16. Re:Multipath broken in debian etch! by strstrep · · Score: 2, Informative

      Debian stable gets bugfixes for significant bugs in later -r1 -r2 releases. This is not limited to security bugfixes. Security bugfixes are the only ones that are pushed out using the security.debian.org repository, however.

    17. Re:Multipath broken in debian etch! by fimbulvetr · · Score: 2, Insightful

      It's called debian stable. It should use stable, tested features. Enabling experimental features and not doing exhaustive testing puts this kernel release directly into the "amateur" camp, which is sad because Debian is a mainstay.

      Do you not understand? Exhaustive testing is done by YOU! and me, and the original poster who seems to have accomplished the epitome of bad administration. It's our job to try and break the betas, alphas and RCs. It's our fault if the final release doesn't work with our exotic setup. It's amazing how the concept of Linux escapes some people. Linux is us. Us is Linux. IOW: We have seen the enemy, and he is us.

      It's labeled experimental for a reason. That means don't use it in production because it may change and if it is not currently broken, it probably will be later.

      No, it means that the code looks good, everything seems reasonable, but we were unable to account for anything more than 99.9% of things. If you think you're outside of 2+ standard devations, please be cautious when trying this option. If your machine isn't anything funky, you'll be just fine.

      And frankly I am tired of seeing the argument of "better than windows". Well, whoop de fucking shit. Windows 2000 is by all reports a better operating system than Vista (in terms of doing what you want it to do) but I wouldn't use either to operate a nuclear power plant. Besides, the EULA forbits it. Explicitly.

      Guess I struck a chord. I'll leave Windows out of this, then.

  4. This release begs the question... by bogaboga · · Score: 2, Interesting
    The question is: -

    Will I be able to have Debian perfectly handle [all] my basic multimedia requirements well by default? I would like to play Yahoo, CNN, ABC, BBC andd FOX video and audio by default. Let a slashdotter inform a soul.

    1. Re:This release begs the question... by Doctor+Crumb · · Score: 4, Informative

      Short answer: no. Long answer: not until those sites release their content in a format that can be legally distributed by debian. "Free Software" does not only refer to the price.

    2. Re:This release begs the question... by MrDomino · · Score: 2, Informative

      By default, no. You'll have to install some extra packages from the non-free repository to play non-free media. However, all your multimedia requirements are just an apt-get install away; flash 9 (which fixes lots of long-standing Linux flash issues), mp3, win32 codecs, etc... I've been using it on my laptop for a while, and it's been pretty solid; I've got no complaints yet.

    3. Re:This release begs the question... by Geoffreyerffoeg · · Score: 3, Funny

      "Means." You keep using that word. I do not think it means what you think it means.

      In particular, the English language is defined by common use, not by some hypothetical Academie Anglaise, and certainly not by Slashdotters.

    4. Re:This release begs the question... by MadMidnightBomber · · Score: 2, Insightful

      <pedant>No, begging the question is assuming the answer. It justs asks the question.</pedant>

      Anyway debian provides a wonderful, stable server distro with the best free software out there. If you want stuff like proprietary audio and video codecs, you can probably get or compile them, but it's not the primary goal of debian. You might be better off with something else.

      --
      "It doesn't cost enough, and it makes too much sense."
    5. Re:This release begs the question... by Professor_UNIX · · Score: 4, Informative

      Will I be able to have Debian perfectly handle [all] my basic multimedia requirements well by default? I would like to play Yahoo, CNN, ABC, BBC andd FOX video and audio by default.
      No, but it's not really the fault of the Debian (or any GNU/Linux distribution) maintainers. Many of these sites are defective by design and only work properly with Windows... sometimes only with a certain version of a Windows web browser: Internet Explorer 6. As a MacOS X user it's a *little* less painful to get a lot of these sites to work in Firefox or Safari in order ot get streaming video to work, but by no means does everything run smooth. The situation is even worse with Linux in regards to how poorly these sites choose to support that platform.

      The only thing I'm happy about is that most of these sites are migrating to using streaming video using a Flash-based player like YouTube does so they just use normal HTTP for the transfer mechanism and are simple to get working through a firewall. In the bad old days I had to worry about shit like RealVideo proxies, Quicktime, RTSP, PNA, Windows MMS, etc. While they're probably more efficient, they require your firewall to have a specialized application proxy and it's just an extra pain in the ass if they break the protocol in a new version. The sites that aren't using a Flash player are just streaming Quicktime/Windows Media over HTTP as well so it has the same effect. The main pain-in-the-ass site I experience is with CNN and FoxNews.

  5. Shoddy rushed release by canadiangoose · · Score: 4, Funny
    So this is what happens when you rush a Debian release out in less than 2 years, eh?

    Seriously though, this is a rather surprising bug to slip through.

    --
    Never eat more than you can lift -- Miss Piggy
  6. Too late? by ezh · · Score: 3, Informative

    Debian has turned into a political zoo of OSS dinosaurs, who are too big and too ancient. They spend lots of time arguing over political issues and raise barrier too high for hew developers.

    During Debian Project Leader (DPL) election campaign candidates were almost in unison looking up to Ubuntu as an example on how to attract new users and developers. With Etch out and new DPL in Debian's goal can be summarized in one phrase: "Let's catch up with Ubuntu"

    How Debian's brand new DPL wants to do this:

    • rework website
    • rework bugtracking system
    • sex up the desktop, and
    • encourage optional desktop releases every 6 months...
    I wonder how they are going to do it... Especially the last bit :-)
    1. Re:Too late? by cymen · · Score: 3, Insightful

      You know I spent a couple of years bitching about how slow Debian is to upgrade. Now I say let them be slow. They serve some market and plenty of other distributions serve those that want more up to date systems. Why change Debian? Slow releases are a core feature.

    2. Re:Too late? by gweihir · · Score: 4, Insightful

      You know I spent a couple of years bitching about how slow Debian is to upgrade. Now I say let them be slow. They serve some market and plenty of other distributions serve those that want more up to date systems. Why change Debian? Slow releases are a core feature.

      Actually, ''testing'' is usually reasonably current. If not, you can roll your own package or lock the package and install your own stuff over it. A bit of a pain, but that way I had X11 support for my 7600GT well before Debian had it.

      I will likely be going to the next ''testing'' in a month or so.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    3. Re:Too late? by swillden · · Score: 2, Informative

      Actually, ''testing'' is usually reasonably current. If not, you can roll your own package or lock the package and install your own stuff over it. A bit of a pain, but that way I had X11 support for my 7600GT well before Debian had it.

      And ''unstable'' is even more current than testing, and not unstable in the common sense of the word. The biggest annoyance I have with unstable is that my periodic upgrades are bigger than with testing, but I have a fast network connection, so I don't care that much. I've been using unstable as my primary work/play platform for about four years now, and the only time it's given me trouble was during a bit of XFree86 upgrade weirdness that lasted about a day.

      Even better, if you're using unstable, it's really easy to pull packages in from experimental, which pretty much always has the latest and greatest releases of everything, so you almost never have to roll your own package or install from source.

      In my experience, I have far less trouble running unstable than I do testing. The downside to unstable is that there is no security team addressing security fixes, but that's rarely an issue for long, since unstable tends to pick up upstream versions very frequently.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  7. Why compete? by rolfwind · · Score: 3, Insightful

    I think this new Debian release is good news for Ubuntu which relies on it, so their next release can be on the 4.0 foundation.... but why would Debian want to compete with Ubuntu? They both have different goals in mind. I love Ubuntu to death, but with the 6 month release cycle, it feels like it's always advancing, but also not as stable as something that I would want to use on a server.

  8. So, which version of Ubuntu is this? by FMota91 · · Score: 2, Funny

    *looks around innocently*

    --
    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C1 bottles of beer on the wall. Take one down, pass it round... Oh, umm...
    1. Re:So, which version of Ubuntu is this? by alienmole · · Score: 4, Insightful

      It's Ubuntu's dad.

  9. Next testing is "Lenny" by cyber_rigger · · Score: 5, Informative


    Debian's next testing version will be code named "Lenny" (from the movie Toy Story).

    http://times.debian.net/1034-Release-update:-Etch+ 1-=-Lenny,-Call-for-Testing,-Time-shift

    1. Re:Next testing is "Lenny" by marcello_dl · · Score: 2, Funny

      So, in my usual way to celebrate a debian release let me say:

      when will Lenny be out?

      --
      ---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
  10. Should I upgrade my new server? by ZakuSage · · Score: 2, Interesting

    I just put it together and installed Sarge yesterday, and I'd rather keep things running stable on it after all that work. Does Etch have any showstopping bugs that would stop a 'apt-get dist-upgrade'? Will it fuck up my apache, proftpd, sshd, or smb servers? Anything I should really know before letting some 600 or so packages change?

    1. Re:Should I upgrade my new server? by fo0bar · · Score: 3, Informative

      Does Etch have any showstopping bugs that would stop a 'apt-get dist-upgrade'? Will it fuck up my apache, proftpd, sshd, or smb servers? Anything I should really know before letting some 600 or so packages change?

      Yes, read the release notes for the answers to those questions. (and much much more! act today!)
  11. Missing package by Bob54321 · · Score: 5, Funny

    Doesn't even include firefox...

    --
    :(){ :|:& };:
    1. Re:Missing package by hondamankev · · Score: 2, Insightful

      These guys are going to analtate themselves into oblivion. I know this is flamebait, but who takes a distro seriously with such jems such as;

      1: "...the Debian Security Team may come to a point where supporting Mozilla products is no longer feasible and announce the end of security support for Mozilla products."

      2: "register_globals ... is now finally deprecated on Debian systems"

      lol?

      It takes a skilled, yet very short bussed person to have any thing to do with such garbage.

    2. Re:Missing package by wouterke · · Score: 3, Informative

      Just for clarity: Debian hasn't enabled register_globals in its default configuration since ages, either. The comment you refer to relates to security updates for PHP. Basically, it says "if you use register_globals anyway, you're on your own; we don't support that"

  12. Might take some searching: by Kadin2048 · · Score: 4, Informative

    Just to follow up, by "non free repository," you'll need something outside the normal Debian repo system -- probably Penguin Liberation Front, certainly nothing U.S.-based -- in order to get that software. (Although I think the Debian/Ubuntu PLF mirrors are down at the moment.)

    In addition to Flash (patent issues) and the Win32 codecs (patents), you'll also need libdvdcss2 (DMCA) if you want to play DVDs, and you might as well get LAME if it's not in there by default (god knows -- probably patents).

    Putting
    deb http://www.debian-multimedia.org/ stable main
    into your sources.list ought to work, but I'm not sure how actively that repo is maintained (it still lists sarge as the stable tree). The VideoLAN people likewise just have instructions for Sarge but hopefully that'll change soon.

    --
    "Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
    1. Re:Might take some searching: by Novus · · Score: 4, Informative

      I am not a lawyer, but I have read the applicable law reasonably carefully, and I'm familiar with the cases mentioned here.

      Redistributing the Flash player is less a patent problem than side effects of a restrictive licence. For example, openSUSE goes out of its way to install browsers compatible with its bundled Flash player; Novell apparently has a deal with Adobe to allow redistribution of acroread and flash-player. Debian seems to circumvent this problem by having the package installer download Flash straight from Adobe. Nice and legal either way (assuming Adobe isn't violating a patent somewhere or something like that, which I doubt).

      libdvdcss2 is trickier. Using Finland as an example of an EU country (applicable law), the situation seems to be that you are allowed to circumvent CSS to watch a movie, but I'm not lawyer enough to tell whether CSS qualifies for legal protection (that depends on whether it's an effective copy protection mechanism, I think) and whether the law requiring the copyright holder/distributor to provide a circumvention device, if necessary, is applicable. You'd also be very hard pushed to argue substantial non-circumventing use, making redistribution quite risky. In conclusion, I think libdvdcss2 users in Finland are safe, but redistributors may have a harder time. Other EU countries should be similar, as most of this legislation originates with the EU.

      The win32 binary codecs are, in part at least, straightforward copyright infringment (unlicensed derivative works), but haven't been subject to any legal action I've heard of. Some of the codecs developed from scratch (e.g. some MPEG variants) seem to need patent licences in some areas; this is the primary cause of problems with MP3 (openSUSE circumvents this by using Real's Helix engine for MP3 decoding, which is licensed).

      In conclusion, the situation is a mess and if you want to be safe, stick to what the major corps tell you is OK. If it isn't, they take the heat.

  13. Is it 1997 or 2007 ? by Muki · · Score: 5, Interesting

    As I was recovering from a spring flu, I was bored enough and decided to upgrade from sarge to etch on my trusty old 600Mhz 256MB Compaq Deskpro. For the most part it went smooth and nice, but what amazes me is why the X stuff is still somewhat awkward. Hardware is certainly not bleeding edge. Maybe I'm just without a clue after a decade of professional multiplatform unix administration, but it sure beats me why X stuff still needs to be this clumsy - we're in year 2007, aren't we - ? Recently I installed two Dell 2900's at work and with Fedora FC6 it was surely as smooth as ever could be. Now someone jumps in and tells that 'Debian is not intended to be easy'. OK, but how is this intended to boost anyone's productivity to battle with stuff that was perhaps ok back in the early 90's ? Debian is such a stable (pun intended) and rock-solid platform to run servers on, I sure like it, but I'd like to see some minor refinements in getting wheels to roll. Used to run sarge at work, used to set up sarge systems for friends small businesses and home use, but have since then moved on to Fedora due to these unnecessary issues. Beat the living daylight out of me but I just don't feel like attacking the xorg.conf or XF....conf with vi anymore "cool" these days. Especially on very common hardware. Other than that, thanks for the debian folks for the release !

    1. Re:Is it 1997 or 2007 ? by Jussi+K.+Kojootti · · Score: 5, Funny

      For the most part it went smooth and nice, but what amazes me is why the X stuff is still somewhat awkward. Hardware is certainly not bleeding edge
      apt is pretty magical, but expecting a dist-upgrade to upgrade your hardware is a bit much.
    2. Re:Is it 1997 or 2007 ? by krmt · · Score: 5, Interesting

      We know it's a pain, and it's a major goal for the next release. The Debian X Strike Force burned the entire release cycle moving first from XFree86 to Xorg, and then from the monolithic Xorg to modular Xorg. By the time it all that was finished, about a year and a half had passed and there was a few months to polish things up for the release. During this time, essentially an entirely new team was built up (only one person from the team that worked on XFree86 in Sarge is still an active member) and there was huge changes as the entire codebase was repackaged for 7.0 and we moved from a private SVN repo to git.debian.org, which was no small feat while we did our best to keep the updates coming at a good pace.

      So expect to see some improvements to this stuff in the next year or so. A lot of work is happening at X.org to improve autoconfiguration, and Debian is moving to help develop it and deliver it to the users. Lenny is going to be really exciting from this point of view.

      --

      "I may not have morals, but I have standards."

  14. Upgrade by Craig+Ringer · · Score: 3, Informative

    The upgrade seems smooth enough, though it's rougher than woody -> sarge was for me. Then again, I'm running much more complex systems now.

    - squid may break if you use it for transparent proxying. It wants the "transparent" option after the listern directive(s) now to enable transproxying, but never used to.

    - the xlibs upgrade does not go well if it can't remove everything in certain directories. In particular, having the jedit package installed screws this up badly. I had to do some manual fixing to get this working.

    - Make really, really sure you have enough room in /var/backups when you upgrade slapd, or it'll require some hand fixing and a db4.2_recover.

    - You'll probably want to use the maintainer's CUPS config, then re-configure it to your specs. The CUPS config has changed a lot and is not really compatible.

    - cyrus delivery socket permissions may need resetting if you use cyrus & postfix.

    Overall, though, for a system as complex as my servers, the process was largely fuss free.

  15. The *only* serious distro by alienmole · · Score: 5, Funny
    I'll see your flamebait and raise you...

    Who takes a distro seriously
    Oh please, does anyone other than script kiddies take any distro *other* than Debian seriously?
    Let's see:
    • There's Gentoo for the script kiddie/ricer set
    • RedHat for the clueless corporate types who're lost if they can't use a purchase order to obtain it
    • Fedora for the lost souls who haven't yet figured out that it's never going to recover from RedHat's abandonment
    • Suse is a German distro owned by Novell -- see RedHat
    • Ubuntu is an ancient African word, meaning "I can't configure Debian" (as someone's sig once said)
    • Lots of other small distros with funny names that won't be around in two years time
    OK, Slackware is great for hobbyists, I'll give you that.

    So anwyay, which are the distros we're supposed to be taking seriously? Besides Debian?
  16. Re:dammit! by alienmole · · Score: 3, Funny

    Try having the CDs mailed to you -- you'll get higher bandwidth that way. 'Course, the ping times suck.

  17. Instant Success! by crhylove · · Score: 3, Insightful

    They could instantly surpass Ubuntu by pretty much adding all the stuff Ubuntu does (it's all FOSS anyway, right?), but making these small changes:

    1. Give users an option to use commercial drivers right off. The new Ubuntu is doing this, but the implementation is still a little rough around the edges, and it's not at all clear that commercial drivers are frequently better than the FOSS ones, which is certainly true for GPU issues.

    2. Default to Iceweasel and Icebird. Debian does this already, so they are a leg up. True FOSS is true FOSS, right? And for some dumb reason Ubuntu still defaults to Evolution.

    3. Make it even easier to turn on compiz/beryl. Still pretty hard even in feisty, requires xorg.conf editing and such... Lame.

    4. Make the default menu look more like windows. You know: "Start" menu, Quicklaunch, App running display (with preview), System Tray, Clock/Calender. Eliminate the top bar that gnome defaults to.

    5. Have four potentially different wall papers for each desktop. The first distro to do this is ahead of the Linux Pack.

    6. Include some really good foss games. You know, games with 3d sound and video, and online multiplayer. Urban Terror is free (as in beer). Use that one, till a better full FOSS alternative comes along. Hell ioquake3 with the original quake 3 demo files would be better than what most distros ship with.

    7. Have Iceweasel, Icebird, Pidjin, Tomboy Notes, and Open Office Writer automatically in the quick launch.

    8. Make it REALLY EASY to get EVERY CODEC.

    9. Install Wine, and while you're at it, fix wine so that you can easily create a launcher on the desktop to any windows app, running under wine, that runs like intended right off the bat.

    10. Have a gorgeous theme by default. For some reason the Ubuntu crowd is obsessed with shit brown. This is the part that is easiest to beat Ubuntu on.

    Do this, and Debian will be THE distro for everyone, and easily supplant Ubuntu, Windows, and Mac OS X.

    Do it not, and remain the odd arcane distro that only a few back room IT nerds use while half assed FOSS OSes (that duplicate each other's efforts, and rarely work that well out of the box) continually lag behind the corporate behemoths that have already got themselves pre installed on 90% of sold computers as it is (Windows/Mac).

    I mean, or just stay private and personal, and to hell with saving the world, which seems like the current Linux mantra.

    rhY

    --
    I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
    1. Re:Instant Success! by cortana · · Score: 3, Insightful

      [Debian] could instantly surpass Ubuntu by pretty much adding all the stuff Ubuntu does (it's all FOSS anyway, right?),

      It is not. Many of Ubuntu's changes involve installing non-free software by default. Debian will never do this. You may feel that this will consign the distribution to obscurity until the end of time; go right ahead, it won't change anything, because Debian is about freedom (and technical superiority) and not market share.

      but making these small changes:

      1. Give users an option to use commercial drivers right off. The new Ubuntu is doing this, but the implementation is still a little rough around the edges, and it's not at all clear that commercial drivers are frequently better than the FOSS ones, which is certainly true for GPU issues.

      What is a commercial driver? There are plenty of commercial drivers that are already in Debian main. It is only non-free drivers that are relegated to the, um, non-free section; they will never be installed by default, because to do so would be to go against everything that the Debian project stands for.

      2. Default to Iceweasel and Icebird. Debian does this already, so they are a leg up. True FOSS is true FOSS, right? And for some dumb reason Ubuntu still defaults to Evolution.

      In fact the default apps are Epiphany/Evolution if you use GNOME and Konqueror/Kmail if you use KDE. As it should be--these apps are designed to work as a part of their respective desktop environments, rather than in spite of them, like Firefox/Thunderbird.

      3. Make it even easier to turn on compiz/beryl. Still pretty hard even in feisty, requires xorg.conf editing and such... Lame.

      As for the software, compiz is packaged for Debian, like any other piece of software. Beryl is not because of the upstream developers' rather... cavaliere attitude towards licensing an copyright. It's a sucky situation, but without a radical overhaul of the US legal system this is not going to change. More details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3 88701.

      As for editing xorg.conf... once composite is readt to be enabled by default, it will be enabled by default and every distribution will be able to use it by default. This will be up to the xorg developers themselves, since it is they who are in the best position to make this decision. Until then, Debian should not make invasive changes such as enabling optional and experimental features of core system software such as xorg.

      4. Make the default menu look more like windows. You know: "Start" menu, Quicklaunch, App running display (with preview), System Tray, Clock/Calender. Eliminate the top bar that gnome defaults to.

      Maybe they should just install XPDE by default? Or just give up and tell people to install Windows in the first place?

      This annoys me a great deal actually. Every distro apart from Debian seems to think that it is necessary to change the default layout of their desktop environments so much that they become unrecognisable to inexperienced users. This makes it impossible to write distribution-neutral instructions on how to do anything in GNOME, KDE, etc. Grr!

      6. Include some really good foss games. You know, games with 3d sound and video, and online multiplayer. Urban Terror is free (as in beer). Use that one, till a better full FOSS alternative comes along. Hell ioquake3 with the original quake 3 demo files would be better than what most distros ship with.

      The games you mention are non-free. As I said above, if you want them installed by default then you are using the wrong distro. Try Ubuntu instead.

      8. Make it REALLY EASY to get EVERY CODEC.

      It is already very easy to obtain every codec that Debian is able to distribute. They are probably even ins

  18. Re:Debian - still alive? by Clazzy · · Score: 4, Insightful

    Ubuntu users do. Ubuntu completely relies on the Debian upstream packages for each release. Ubuntu them patches everything and submits the patches back to Debian. You could argue that Ubuntu could do all this by itself but Debian is massive and is known for its high packaging standards which is a good thing. Ubuntu and Debian, at the end of it, are two different things with two different goals. Debian wants stability, Ubuntu wants the latest technology and packages. Ultimately, Debian should still be important for servers and Ubuntu for the desktop. Just don't dismiss Debian yet.

    --
    If we can hit that bull's-eye, the rest of the dominoes will fall like a house of cards... Checkmate.
  19. Re:Q: can I run it on my machine? by Gleng · · Score: 2, Informative

    Yeah, it should run fine on that machine. I've run Debian on a 120MHz Powermac 7200 and a 1.33GHz G4 Mac mini, and it was sweet on both.

    Any PowerPC based computer should run Debian fine.

    --
    "Proudly Posting Without Reading The Article"
  20. That's sad, really. by Tyln+Sylverwind · · Score: 2, Insightful

    I've witnessed attempts by various individuals to fundamentally alter the goals of Debian. Most common is trying to make Debian a more "desktop-oriented" distribution. Good attempts turn out as separate distributions. Honestly, that's how it should stay.

    See, Debian not only welcomes child distributions, it thrives on them.

    http://www.debian.org/misc/children-distros

    At some point in time, I would encourage consideration of Debian's slogan, "The Universal Operating System".

    Debian has been and always will be an operating system that equally (as in equity) targets all applications; that's why child distributions are necessary, and why Debian Unstable is so damned important. Child distributions are required to pull the Debian project in a productive direction. Debian Unstable is required to tie the required functionality of child distributions together and, in turn, propagate the benefits to all parties involved.

    It doesn't make sense to take a piece of software to any sort of bleeding-edge when it will be deployed world-wide on Debian servers and Debian routers. Furthermore, the fact that a child-distribution is already working to "sex up the desktop" is evidence that Debian need not take initiative in such a direction; it's already involved.

    --
    I use Debian, because nothing else meets my needs.
  21. Re:Why use this over ubuntu? by halovaa · · Score: 2, Interesting

    I have two friends, both of whom have recently switched to Linux for everything except a few games that can't be handled with Cedega. I didn't push them into it, they just grew frustrated with Windows and knew that there were alternatives. One installed Debian (AMD64 + ia32 chroot even!) and I elected to install Kubuntu (Edgy 32-bit) on the other's as I figured it would be more noob-friendly. The guy who uses Debian said "It starts off broken and you fix it, but then it stays fixed, while Windows starts off fixed but then breaks itself." He also liked that it would warn him about doing something stupid, but would trust him enough to let him do it anyway. He's now perfectly happy with it, rapidly flipping a Beryl/Compiz cube around to IM people while playing WoW. He uses Unstable, he runs beta software, he fiddles with things. Don't get me wrong, the Ubuntu friend definitely preferred it over his struggles with Windows. He told me, when he found himself booting into Windows to play WoW that he would ask himself "Why can't Windows be Linux?" The problems come because Ubuntu is just less flexible than Debian. First, it supports a much more limited set of packages officially than Debian. This requires adding the universe and multiverse repositories, because he didn't want only the most useful packages, he wanted to try anything that sounds interesting. Cedega wasn't working well with WoW and the three of us thought it might be because of the 8xxx series drivers being installed instead of the 9xxx series. Now the Debian versions of these were only available in Experimental, but with some help from me, the Debian guy was able to install them easily enough, and nothing broke. In Ubuntu however, only Feisty had the 9xxx series. From experience, I've learned that you can't just upgrade one or two packages to a newer version in Ubuntu like you can in Debian. Things like libc6 change versions from release to release, and the whole system has to be upgraded. I figured that Feisty should be near enough stable that upgrading to it wholesale should go pretty well. We even used the update manager provided with Ubuntu. Incompatible packages ended up installed, as versions were moved into and out of Feisty (I think), and right now his system is usable, but will require some extensive fixing by me to get apt working again. The lesson? Ubuntu is great if you do what they expect you to as a normal desktop user. If you want to do something less common, it's not as flexible as Debian and can get in your way.

  22. Re:Why use this over ubuntu? by brufar · · Score: 3, Insightful

    Debian - Gives the user control to choose what they want to use, more packages more options..
    Ubuntu - Makes most of the initial choices for the user..

    Debian - manual configuration of a lot of items..
    Ubuntu - a bit better at auto-configuration of hardware.

    Debian - Etch 20,400+ Packages in the official repository
    Ubuntu - Fiesty I think it's around 6000 Packages but can't find a stat anywhere to confirm exact munber.

    Debian 13 hardware Architectures i386, x86-64, PowerPC, 68k, SPARC, DEC Alpha, ARM, MIPS, HPPA, S390, IA-64, AMD64, Intel EM64T
    Ubuntu 3 Hardware Architectures i386, AMD64, PowerPC,

    I've used child distros in the past an always ran into problems. I would then switch to the parent distros to get away from the problems.. So I use Debian rather than one of it's numerous children to prevent a repeat of my previous experiences. http://www.debian.org/misc/children-distros

    --
    far...out
  23. Re:No, it's because a catastrophically bad system by ljaguar · · Score: 2

    in this case, all they had to do is not enable equal cost multipath caching.

    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.