Slashdot Mirror


The Debian System Explained

An anonymous reader writes "XYZComputing has a great interview with Martin F. Krafft, the author of "The Debian System". From the article: 'Despite Debian GNU/Linux's important role in today's computing environment, it is largely misunderstood and oftentimes even discounted as being an operating system which is exclusively for professionals and elite users. In this book Krafft, explains his concept of Debian, which includes not only the operating system but also its underpinnings. Debian is not only a robust and scalable Linux distribution, but it has many other features which are worth looking into, like its open development cycle and rigorous quality control.'"

62 of 281 comments (clear)

  1. Debian has always been the best by XMilkProject · · Score: 5, Informative

    I'll use nothing other than Debian and Debian Based distro's. Ubuntu and Kubuntu are nice, as they are based off debian, have the massive package base available, but also are updated a bit more often.

    --
    Big ones, small ones, some as big as yer 'ead!
    Give 'em a twist, a flick o' the wrist...
    1. Re:Debian has always been the best by erikdalen · · Score: 2, Informative

      they did that ages ago in testing and unstable.

      They promised to keep xfree86 in the stable "sarge" release, and that's what they did. The next release will have Xorg though. And everyone can run it right now, you don't have to wait. I'm running Xorg 6.9.0 on my debian box. /Erik

      --
      Erik Dalén
    2. Re:Debian has always been the best by sameeer · · Score: 3, Insightful

      The ease of using Debian based systems in terms of installing software, and easy updates might be just the thing which'll boost linux to the desktops of the majority of computer users who do not want to learn or be exposed to the intricacies of the operating system before using it.. we shall have to just wait and see..

  2. Debian in a Nutshell... by Anonymous Coward · · Score: 5, Funny

    ...RTFM !!

    Ah, it is still good though.

  3. All I know is... by TeachingMachines · · Score: 5, Informative

    Debian 3.1 is a dream. Easy to install, no more updating (except for security updates), and rock solid as my desktop OS. FreeBSD was similarly solid, but the package management and printer control for Debian is just so darned easy. Hats off to Debian!

    --

    The Death Penalty: Killing people to show others that killing people is wrong.
    1. Re:All I know is... by colinbrash · · Score: 2, Funny

      Hats off to Debian!

      Pun intended? ;)

    2. Re:All I know is... by misleb · · Score: 3, Informative

      Eh?

      apt-get install cupsys cupsys-driver-gimpprint cupsys-client cupsys-pt

      http://localhost:631/

      Login as root and setup a printer.

      Or is the problem finding the right device to use?

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    3. Re:All I know is... by misleb · · Score: 2, Informative

      As a long time Debian user trying out FreeBSD, I must say the package management is pretty bad in FreeBSD by comparison. However, I think FreeBSD makes up for it by always having cutting edge ports available through cvsup. Sarge is great now, but in a year or two, you're going to be lamenting not having the latest packages available to you without backporting headaches or risking your solid system by mixing unstable packages with stable.

      -matthew

      --
      "THERE IS NO JUSTICE, THERE IS ONLY ME." -Death
    4. Re:All I know is... by An+Audience+of+One · · Score: 2, Insightful

      If you are going to install cutting edge ports from cvs on freebsd, you should compare it to installing packages from Debian Unstable, not the stable branch. If you are willing to put up with possible system-breaking changes from newer versions being installed, then Testing and Unstable (currently Etch and Sid) are there for you. If you want a guarantee that once setup your system will stay that way, you want Debian Stable.

  4. As interesting as the technology by Anonymous Coward · · Score: 5, Insightful

    The organization is as interesting as the technology. Lots of people are willing to put in lots of volunteer time.

    I wonder how long it will be before the business schools start to take notice of successful open source projects and learn a bit about management.

  5. Is Debian a fad? by Anonymous Coward · · Score: 2, Interesting

    Interesting. I went through the same linux phases...

    slackware, red hat, suse and now debian. Looked at Gentoo a bit but stuck with Debian.

    1. Re:Is Debian a fad? by level_headed_midwest · · Score: 2, Insightful

      I went through a different set of phases:

      Debian (Woody) -> SuSE -> Ubuntu -> SuSE.

      Debian Woody was NOT the right distro for somebody to start out on Linux with. I thought I had mis-installed it when all I got was a command line- I didn't know I had to startx. So I went to SuSE and ran with that for a year and a half. When my HDD crapped out, I thought I would give Ubuntu a try, and it stayed with me a couple of months. It was nice, but suspending was a ***** and OpenSuSE 10.0 finally became usable. So I went back to it. APT is wonderful, Debian-based systems are lighter, but the only distro that always works well with little dicking around is SuSE.

      --
      Just "gittin-r-done," day after day.
  6. Other Distros by IAAP · · Score: 4, Interesting
    FTFA:Many people actively involved with Debian development are working as system administrators themselves. Thus, they know very well what their own needs are, and in case Debian doesn't meet them, they are in the position to fix that. However, ideally, one should not have to be a Debian contributor to successfully deploy Debian in production environments.

    I'm not an admin - outside of my own hacking at home. But, help me out here, is Debian more of an enterprise-admin friendly-scalable distro than, say, RedHat Enterprise?

    From what I've seen between various distros(No Debian), there's their add-ons (desktop add-ins, installation software, etc...), and then there's just Linux, XFree86, and all of the GNU software stuff. Is Debian that much better whe it comes for day to day operations?

    1. Re:Other Distros by benjamindees · · Score: 3, Insightful

      is Debian more of an enterprise-admin friendly-scalable distro than, say, RedHat Enterprise?

      It depends on your definition of "enterprise". And it really depends on the admin. For your typical, point-and-click, illiterate computer monkey "enterprise" admin who only knows enough to install updates, reinstall the entire OS, and call for outside help, RedHat is perfect. In fact, it appears that this is RedHat's primary market.

      For admins who know what they're doing and can invest time in making their jobs easier and more productive, however, Debian is an absolute dream.

      --
      "I assumed blithely that there were no elves out there in the darkness"
    2. Re:Other Distros by Kjella · · Score: 4, Informative

      From what I've seen between various distros(No Debian), there's their add-ons (desktop add-ins, installation software, etc...), and then there's just Linux, XFree86, and all of the GNU software stuff. Is Debian that much better whe it comes for day to day operations?

      Well-tested, stable packages with no dependency issues or known security bugs and security patches, yes. Proprietary tools? No. Debian strictly follows the Debian Free Software Guidelines, which means that anything in their distro any other distro could just take. I can't really speak for everything you need in an enterprise setup but as a home server & remote X desktop it is excellent.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Other Distros by buchanmilne · · Score: 2, Insightful

      For me it's all about will I be able to build my tarballs

      Build tarballs?

      In an enterprise environment?

      You must be kidding.

      Red Hat has lots of tools that make deployment quick and easy, *especially* for the admins who know their stuff.

  7. Shhhhhhhh!! by Anonymous Coward · · Score: 5, Funny

    Don't tell everyone how AMAZING Debian is, please! I get this strange (probably very sick) psychological aversion to seeing things I feel are part of my ingroup assets become popular. As a Debian user of 7 or 8 years I get a little nervous at this. My choice of (vastly superior) operating system is what makes me feel different. Have a little mercy on a nerds elitist insecurities please! Im the guy who always discovered underground bands years ahead of everyone else, and when they finally became mainstream I wanted to disown them. My 'discovery' felt _violated_ by the hoards of unwashed sheep jumping on the wagon. 20 years as a 'geek' and now I hear that 'geek is chic'. Time to become a merchant banker. Stop following me around you horrible unoriginal soulless people!! Find something of your own. Debian is the best kept secret in the world to me right now, don't go around telling the oiks all about it or they'll hijack it, misrepresent it, and corrupt it by dragging it down to the lowest common denomiator like everything else they touch. Next thing I know some techno wannabe will be coming up to me in the street and saying "Hey, have you heard about this really awesome new operating system called Debian Linux!" ....Smack!!

    Windows is the choice people! Windows is the best, trust me. Debian is rubbish!

  8. Huh? by IamTheRealMike · · Score: 2, Interesting
    Debian is not only a robust and scalable Linux distribution ...

    This sort of thing reminds me of Joel Spolski's opinion on advertising:

    The idea of advertising is to lie without getting caught. Most companies, when they run an advertising campaign, simply take the most unfortunate truth about their company, turn it upside down ("lie"), and drill that lie home

    If Debian is so scalable, why does it take them so much longer than any other OS vendor to simply do a release? How comes the software even in the "unstable" version is so often out of date? If it's so robust, how comes that shortly after their last stable release it was revealed that their entire security infrastructure revolved around one man, and that when he went on holiday the flow of updates simply stopped?

    It seems to me that if you wished to advertise Debian, scalability and robustness would be the last qualities you'd choose to highlight. Instead you might want to focus on its dedication to the ideals of free software (that doesn't entice many people to install it though ...) or the fact that it runs on so many CPU architectures (hmm ... ditto). Actually, I can't think of any compelling reasons for the majority to run Debian directly. I say this even though I use Debian on my own server .... the original reasoning for this was that I felt at least the community was big and stable so there would be a reliable supply of security updates. That was before I found out about the size of their security team and the bandwidth bottlenecks on their servers (eg, Xfree update). After that I found myself wishing I'd installed Red Hat instead.

    I guess many people agree with me because these days I see very few people advertising Debian as the Wonder OS that it was promoted as when I first got into Linux. These days people tend to promote it by pointing to the (significantly more popular) operating systems built upon it, like Ubuntu or Knoppix. Of course, it's not exactly great PR to promote yourself as the base for what are effectively (policy and project-wise) forks, but marketing was never Debians strong point ...

    1. Re:Huh? by rca66 · · Score: 2, Insightful
      If Debian is so scalable, why does it take them so much longer than any other OS vendor to simply do a release?

      "scalable" does not mean from the developer's view, but from the user's view.

      I guess many people agree with me because these days I see very few people advertising Debian as the Wonder OS that it was promoted as when I first got into Linux.

      When reading the interview, I would guess: neither would Krafft call it "Wonder OS".

      Of course, it's not exactly great PR to promote yourself as the base for what are effectively (policy and project-wise) forks, but marketing was never Debians strong point ...
      The quote you refer to was not from Krafft.
    2. Re:Huh? by no+reason+to+be+here · · Score: 3, Insightful
      If Debian is so scalable, why does it take them so much longer than any other OS vendor to simply do a release?
      1. scalability has nothing to do with release time.
      2. the biggest OS vendors new OS longhorn is due out when, exactly? and how far past due?

      just sayin'...
  9. Debian rocks -- The book less so by peeping_Thomist · · Score: 4, Informative

    I've been using only Debian for about 5 years. It's the best. I totally support the community, and the philosophy behind Debian. Debian Stable is great for some purposes, and Debain unstable is great for others.

    I've been reading Martin's book (it cost me $30), and unless the second half has a lot more in it than the first half does, there's not much there that an experienced user of Debian doesn't already know. So if you're already an experienced Debian user, the news is good: you already probably understand a lot more than you think you do! If you're not already experienced with Debian, what are you waiting for?

    --
    Anything worth doing is worth doing badly -- G.K. Chesterton
    1. Re:Debian rocks -- The book less so by alfino · · Score: 3, Informative

      I would love to hear suggestions as to what's missing. feedback at debianbook.info .

      --
      echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
    2. Re:Debian rocks -- The book less so by jilles · · Score: 2, Insightful

      More specifically, debian stable is (really) good for servers that don't need the latest and greatest. It sucks for workstations because you'll end up being one or two major versions behind for the most crucial desktop packages, including significant feature, stability and security improvements that go into these packages.

      Debian unstable is good only for non production workstations. Specifically it doesn't have security updates; it will be in a more or less broken state most of the time (which may or may not affect you depending on which packages you use). Debian testing is only slightly better, you still don't get the security updates and buggyness still is an issue. Blindly updating a debian testing install is a ticket to disaster (been there, done that).

      What's frustrating for new Debian users is that the Debian developer community is not really that interested in them. If you can get it to work good for you, if you can't RTFM. Also it is a safehaven for the ideological elements in the linux community. You know, the ones that insist on speaking of Gnu/linux. Dealing with the more extremist types in this community can be tedious. Lots of people use Debian for ideological reasons rather than pragmatic reasons. Recently the pragmatic part of the community made a mass defection to ubuntu (debian derived).

      I'd recommend anyone looking for production use of debian in a desktop environment to only consider ubuntu. For small scale servers debian stable is a good option: you don't get the bloat of the big vendor stuff and it just works. For large scale servers, use something with support and reputation: red hat, suse are good options and all major vendors support them. Only use Debian on large scale production servers if you are willing, permitted and qualified to run it. Because if the shit hits the fan it will be you cleaning up the mess with noone committed to support your mess other than you.

      --

      Jilles
  10. Re:Timeline in perspective by alfino · · Score: 2, Interesting

    I was born in 1979 and I became a beta-tester with 13. I don't think Microsoft actually ever cared about my age. I was contacted about beta testing because I completed all 6 MCPs required for the MCSE in a single day, or at least so the email said.

    I still have the reports I sent to them as part of the beta testing, and mind you, even now they are everything but childish. But they clearly come from someone who was used to administering nets for 50-or-so users with Netware, and Netware wasn't the direction they wanted to take with NT 4.

    For instance, I proposed to allow specification of ACLs per user, rather than per resource. Who here has used Netware and didn't come to love this feature?

    -- martin

    --
    echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
  11. Great book, too bad about the software by FishandChips · · Score: 4, Interesting

    Kudos to Martin Krafft for writing his book. Many dream but few ever get it together ...

    That said, I spent most of 2005 running Debian Unstable and Debian Testing on different systems and ended up finding both overrated and generally a disappointmennt. Debian was too demanding of time and needed seemingly endless fiddling around and careful management. It also took a lot of time to set up, though admittedly that is a one-off when an installation is still fresh. More important, the Debian developer community seemed shot through with an obsession with doing things the Debian way, with college-level debates (aka rows), with considerable disdain for new users and with frankly pretty obscure things of little interest to many in the everyday world. Overall, I began to wonder if some of these guys would recognize an end-user if they fell over one and my faith in the Debian way rapidly dwindled.

    None of this should detract from Krafft's achievement, though. It's a heck of a good thing to have done. I do find it a little odd that he should recommend that new users try Ubuntu rather than Debian. One is tempted to ask: what's the problem whereby they can't use Debian, then?

    For myself, I've now gone back to another distro. It's pretty nearly as capable as Debian, with the difference that its devs are technical experts who confine themselves to delivering what works. A distro that puts out for its users without striking tiresome poses or co-opting its users into politics of some kind is much the more preferable, for me at least.

    --
    Las qué passoun
    tournoun pas maï
    1. Re:Great book, too bad about the software by alfino · · Score: 2, Informative

      > I do find it a little odd that he should recommend that new users try Ubuntu
      > rather than Debian. One is tempted to ask: what's the problem whereby they
      > can't use Debian, then?

      I try to answer this question in the introduction of my book, section "Target audience". You can obtain the first chapter from http://debiansystem.info/about . Now I hope you guys aren't going to kill my server.

      --
      echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
    2. Re:Great book, too bad about the software by Chalex · · Score: 3, Insightful
      That said, I spent most of 2005 running Debian Unstable and Debian Testing on different systems and ended up finding both overrated and generally a disappointmennt. Debian was too demanding of time and needed seemingly endless fiddling around and careful management
      This is the perfect example of not understanding "The Debian System". YOU aren't supposed to use unstable. You're not even supposed to use testing. If you don't want to have to fiddle with the system, use "stable". That's what it's for. This is clearly explained in a number of places in the documentation.

      If you really want to use the latest software, why not use Ubuntu? They do all the fiddling for you.

    3. Re:Great book, too bad about the software by alfino · · Score: 3, Informative

      One thing I did not specify -- as I did not mention Ubuntu in the introduction:

      I recommend Ubuntu to new users of Linux because in my experience, most of them were just that: new users who wanted to read their email, author documents, and use their laptops power management at night. Sure, all of this is very possible with Debian, but IME not really for the newbie.

      Here, Ubuntu has done a good job at making Debian more accessible. That is all. And being accessible to the Linux newbie just isn't "Debian's place" IMHO. We make a stable operating system that is a reliable tool for those who know how to use it. We don't want bells and whistles and lots of automatic stuff making it easier for the new users.

      I would not recommend Ubuntu to someone who has the potential to climb the curve quickly. And of the dozens of people I've switched to Linux/Ubuntu in the past months, most have already switched to Debian. I think that's a natural thing to do as you exceed the offerings of Ubuntu, which is am operating system that trades much flexibility for the tight integration and beautification it has.

      Anyway, to each their own. Going for Ubuntu is probably not a mistake. Heading right for Debian isn't either, but you're in for some more work.

      --
      echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
    4. Re:Great book, too bad about the software by FishandChips · · Score: 3, Interesting

      This is the perfect example of not understanding "The Debian System". YOU aren't supposed to use unstable. You're not even supposed to use testing. If you don't want to have to fiddle with the system, use "stable". That's what it's for. This is clearly explained in a number of places in the documentation.

      Actually, that's the perfect example of why Debian doesn't work for everyone, for stictly my two cents. Not every user is in it to be hectored (an obsession with the Debian way, in full caps) or treated with disdain (must be too stupid to have read any documentation, etc.). Personally, I use Linux to get away from all that stuff about we own your ass so do what we say.

      To answer another reply, I now use a mucho tweaked SuSE. Works for me. Any number of other distros, including Debian, may well work better for you, maybe more so now Martin Krafft has given everyone the gift of a full-up guide to Debian.

      --
      Las qué passoun
      tournoun pas maï
    5. Re:Great book, too bad about the software by FishandChips · · Score: 2, Funny

      So, do you like tweaking or not?

      Lol. I'd like it from Scarlett Johansson or even Allison Janney but not alas from your average geek. :)

      --
      Las qué passoun
      tournoun pas maï
  12. Re:Debian SUCKS on SPARC --- won't install, period by raynet · · Score: 3, Interesting

    I have couple Sun Ultra 1 workstations and had no trouble installing Debian Linux (Sarge) on them. Just checked couple faqs and howtos to be sure my hardware was supported and how to change screen resolution and how to patch firmware to support 64-bit mode (though I think it was Solaris that required the firmware patch to even boot).

    Either you did something wrong or just happened to have an SPARC that wasn't supported or tested.

    --
    - Raynet --> .
  13. Re:Debian SUCKS on SPARC --- won't install, period by Spit · · Score: 2, Informative

    Debian installs fine on my Sparcs, but Linux kernel crashes on Sparc. Debian patch or vanilla tarball, you can get the kernel to shit within 30 minutes of running crashme. Try it.

    OpenBSD is much better for these old Sparcs, hopefully the MP will come up to scratch for the MBus boxes.

    --
    POKE 36879,8
  14. Re:Debian SUCKS on SPARC --- won't install, period by m50d · · Score: 3, Informative
    I installed woody on an SS10 with no difficulty at all (It has no cdrom drive, so I couldn't (at that stage) install sarge directly). Then I just did a dist-upgrade to sarge, which requires a bit of jumping through hoops as both the kernel and libc need to be upgraded and either is incompatible with the other, but the procedure is clearly explained on the website and I managed it with few difficulties.

    I have since installed gentoo, using the standard install process, and it's worked pretty much perfectly - only gripe I have is it won't automatically generate an initrd with the right scsi modules like it can on x86, but I can live with that. So much for no linux distro having supported it for half a decade - I don't think gentoo's even been around that long.

    --
    I am trolling
  15. Debian best by mislam · · Score: 2, Informative

    Debian 3.1 is really great. True, they have taken a long time to make this release but as I see it it is a great OS for the server. I am running it on my server and very happy with almost no fiddling I had to do with it. However, trying to run it on my workstation was a different story. Mainly because of all the wifi issues I ran into. But that is not solely debian's problem. Fedora had the same issue. So if you are looking for something rock solid for your server, go with debian. If you want something on your workstation supporting tons of new new hardware and offer opportunity for endless finddling, go with Fedora Core 4. Just my 2 cents.

  16. The Community Sucks by c_spencer100 · · Score: 5, Interesting

    I've never had anything against Debian itself. My problem, as with a lot of other people, was always the arrogance that just seemed to ooze from the average Debian user. If you don't know what I'm refering to, then you probably relatively new to the Linux Community. It seemed for the longest that every question posted on every forum yielded the answer "get Debian". Debian's problem was NEVER being misunderstood - it was being misrepresented by the zealots that actually think their pretentous attitude represents the Debian Community as a whole.

    1. Re:The Community Sucks by Penguinisto · · Score: 5, Funny
      ...you've never owned a Mac before, have you?

      /P (a Mac user who, umm, "occasionally" finds trouble with the zealotry of his Cupertino-facing brethren...)

      --
      Quo usque tandem abutere, Nimbus, patientia nostra?
  17. Re:Debian SUCKS on SPARC --- won't install, period by MacJedi · · Score: 4, Informative
    debian:~> uname -a
    Linux debian 2.4.26 #1 Sat May 1 18:58:40 EDT 2004 sparc64 GNU/Linux
    debian:~> cat /proc/cpuinfo | head -n 1
    cpu : TI UltraSparc IIi (Sabre)

    I'm not saying that your problems aren't real, but Debian certainly supports Sparc and in my experience, it does so very well. I've had nothing but great success with Debian and Sparc, including the installer. Perhaps you should consider filing a bug report with the Debian Installer team. The architectures which have fewer users, receive fewer bug reports. How can you expect them to fix a bug they may not know exists?

    As an aside, there is a good chance Sparc will be cut from Etch, so you may not have to worry about Debian "pretending to support SPARC hardware" in the future.

    --
    2^5
  18. Re:yeah, but you can't really search for packages by Grey+Ninja · · Score: 4, Informative
    I have an alias set up that allows searching from the command line quite easily.

    alias s='apt-cache search --names-only'


    Then, to look for something like... libvorbis, I would just have to do this:

    s libvorbis


    And it returns this:

    libvorbis-dev - The Vorbis General Audio Compression Codec (development files)
    libvorbis0a - The Vorbis General Audio Compression Codec
    libvorbisenc2 - The Vorbis General Audio Compression Codec
    libvorbisfile3 - The Vorbis General Audio Compression Codec
    libvorbis-ocaml - OCaml bindings for vorbis library
    libvorbis-ocaml-dev - OCaml bindings for the vorbis library
    libvorbis-perl - Perl extension for Ogg Vorbis streams
    libvorbisfile-ruby - Ogg Vorbis support library for Ruby
    libvorbisfile-ruby1.6 - Ogg Vorbis support library for Ruby1.6
    libvorbisfile-ruby1.8 - Ogg Vorbis support library for Ruby


    Easy as pie.
  19. Debian is for hackers; Ubuntu is for users by Russ+Nelson · · Score: 2, Informative

    I've run into far too many Debian users who have contempt for anyone who knows less than them that I have to assume it's an integral part of Debian culture. I would never recommend Debian for anyone who isn't an expert. If you like Debian anyway, and want to gain the best parts of Debian, recommend that mere users use Ubuntu.
    -russ

    --
    Don't piss off The Angry Economist
    1. Re:Debian is for hackers; Ubuntu is for users by dbcad7 · · Score: 2, Interesting
      I've been around the block a few times with Linux, but I am by no means an expert, and I use Debian as my primary OS at home. I think it is true not only for all Linux distro's but the Windows side too.. that you will run into "power users" who will try and demean someone with their superior knowledge when you are asking a question.

      It is my experience, that Debian is no harder to learn and use than Ubuntu. Ububtu has some polish "out of the box" that Debian doesn't, but really they are not that different. I think any Ubuntu user could run Debian with about zero hours training

      As to getting help from other users, I haven't really had any problems with contempt. When I have looked for help, I went to linuxquestions.org because I was used to going there on other distros.. so perhaps it is different where you looked for help.

      --
      waiting for ad.doubleclick.net
  20. Re:Debian Based by alfino · · Score: 2, Informative

    1.5 is in unstable already, which means it'll soon trickle into testing. It also means that the next Ubuntu release in April will have it.

    --
    echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
  21. Modifying packages to conform to FHS = bad by grosskur · · Score: 4, Insightful
    I was a Debian user for four years; I recently switched away because I got fed up with all the downstream futzing they do to their packages. I understand Debian's need to ensure high-quality packages, but making gratutious changes to package interfaces (e.g., moving and renaming files) just to conform to a hardline FHS policy is extremely detrimental in the long term.

    Cross-platform compatibility is essential. If the upstream Apache maintainers say Apache can be stopped with apachectl stop, Debian should damn well support this interface. I don't care if they provide /etc/init.d/httpd stop in addition, but they should support the standard interface. This makes life infinitely simpler for people who deal with many different systems---they don't have to keep relearning things. It also makes things simpler for people offering support to Apache users.

    The tremendous benefits of cross-platform compatibility come from a package's interface being exactly the same on every system. It is a relatively minor benefit for different packages to have similar interfaces. Breaking cross-platform compatibility, as Debian does, for the sake of cross-package similarity is a horrible idea.

    I should point out that I'm picking on Debian here because they are especially bad about this, but almost every major Linux distribution is guilty of unncessarily violating cross-platform compatibility in some way.

    1. Re:Modifying packages to conform to FHS = bad by dondelelcaro · · Score: 2, Insightful
      The tremendous benefits of cross-platform compatibility come from a package's interface being exactly the same on every system. It is a relatively minor benefit for different packages to have similar interfaces. Breaking cross-platform compatibility, as Debian does, for the sake of cross-package similarity is a horrible idea.
      I should point out that I'm picking on Debian here because they are especially bad about this, but almost every major Linux distribution is guilty of unncessarily violating cross-platform compatibility in some way.
      The FHS is what defines "cross-distribution" as well as "cross-package" compatibility. Packages that choose to stick things in locations which do not comply with FHS are broken. It's the job of distributors to fix these issues, and then try to get them accepted upstream. Our users expect packages to follow the FHS. If you'd rather have something else, well, feel free to use another distribution or LFS or something.
      --
      http://www.donarmstrong.com
    2. Re:Modifying packages to conform to FHS = bad by roystgnr · · Score: 2, Insightful

      Follow the instructions for installing from source, and you will have everything accessible under /usr/local/qt; install the Debian packages, and you will see they changed the name to /usr/share/qt3.

      So they don't clutter up my /usr/local/ tree, a directory for things I've installed by hand, with automatically installed packages? Good for them. The Filesystem Hierarchy Standard says "The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated," and I'd hate to use a distribution that violated that safety.

      Why does the directory location of qt matter that much to you anyway? Fedora has it in /usr/lib/qt-3.3 and everything's working fine. In fact, I could put qt in /home/roystgnr/qt/ if I want, define QTDIR and my linker path accordingly, and unless your qt-using software is broken it should work. We bitch enough about broken software that unnecessarily requires Administrator access on Windows; there's no reason to go any easier on software that unnecessarily requires root access on Linux.

      Debian using /usr/share/qt3 is a little worrisome, though. */share/ directories are supposed to be for architecture-independent files, and qt library binaries by definition include compiled code. I hope Debian's got that under /usr/lib where it belongs.

    3. Re:Modifying packages to conform to FHS = bad by Darlock · · Score: 2, Insightful

      Don't let the Debian zealots get to you as you are correct. Debian likes to do things it's own way and it makes things very hard when dealing with other distros.

      I will say though that Debian was the first distro that I ever used and I was deep into it for 2 years. It was smoking on my pentium pro at the time. =) I absolutely loved apt-get but eventually I got sick of fighting with the system.

      I'm running Gentoo now.

    4. Re:Modifying packages to conform to FHS = bad by cortana · · Score: 2, Insightful

      Personally I can't stand Qt, but a cursory examination reveals that you can just pretend that Qt is installed to /usr/share/qt3 instead of /usr/local/qt3:

      $ ls -l /usr/share/qt3/
      total 16
      drwxr-xr-x   2 root root 4096 2006-01-11 02:53 bin
      drwxr-xr-x   3 root root 4096 2005-10-04 11:30 doc
      lrwxrwxrwx   1 root root   17 2006-01-11 02:52 include -> ../../include/qt3
      drwxr-xr-x   2 root root 4096 2006-01-11 02:52 lib
      drwxr-xr-x  61 root root 4096 2006-01-11 02:53 mkspecs
      lrwxrwxrwx   1 root root   21 2006-01-11 02:52 plugins -> ../../lib/qt3/plugins

      $ ll /usr/share/qt3/lib
      total 0
      lrwxrwxrwx  1 root root 25 2006-01-11 02:52 libqt-mt.prl -> ../../../lib/libqt-mt.prl
      lrwxrwxrwx  1 root root 30 2006-01-11 02:52 libqt-mt.so -> ../../../lib/libqt-mt.so.3.3.5

      ... and so on. The symlinks shipped by the Debian packages ensure compatibility with the (IME, inflexible and annoying) layout where everything is in a single directory.

    5. Re:Modifying packages to conform to FHS = bad by cortana · · Score: 2, Informative

      Relax, the only regular files under /usr/share/qt3 are arch-independent. Most of the files in there are symbolic links to the files' proper locations, presumably for the benefit of broken software/users who demand that everything lives in one directory. :)

    6. Re:Modifying packages to conform to FHS = bad by cortana · · Score: 3, Informative
      For example, how do we find libssl.so on an FHS-compliant system? Is it /usr/lib/libssl.so or /usr/local/lib/libssl.so, or even /opt/openssl/lib/libssl.so? The FHS ensures we will never have a simple, consistent name, like we would have if the package author madated it to be /package/host/openssl.org/openssl/libssl.so.
      Bald erdash. Say you want to run a binary that declares in its DT_NEEDED that it requires SONAME libssl.so.0.9.7. ld-linux will consult ld.so.cache, which contains the mapping of DT_SONAME -> library files. As the user, I don't give a damn where libssl.so.0.9.7 actually lives--the dynamic loader takes care of that for me.

      Contrast this with DJB's crackheaded /package system. My binary again has libssl.so.0.9.7 in DT_NEEDED. But now that there is no fixed set of directories for the loader to search for libraries; I am expected to edit /etc/ld.so.conf and re-run ldconfig every time I install a new library.

      An alternative is to forsake the shared library cache alltogether, and maintain an ever-growing collection of PATH, LD_LIBRARY_PATH, etc, environmental variables. If I enjoyed hammering nails through my dick in this way, I'd swich to Solaris where this insanity seems to be accepted. :)

      Hey, maybe I should I just switch to Windows, where the solution to this problem is for every app to ship private copies of the shared libraries that it requires in the same directory as its binaries, wasting disk space and causing uncounted security problems... :)
    7. Re:Modifying packages to conform to FHS = bad by rekt · · Score: 3, Interesting
      i can't believe this is being moderated as Insightful. What are you mods thinking!?

      i'm a huge fan of djb's work, and i use his software (and i use Debian), but quoting his theories about cross-platform compatibility as support for your argument is pretty weak. djb's strong suit is his technical and mathematical rigor, not his infamous interpersonal skills.

      For those of us who maintain more than a handful of machines, cross-package similarity is a real and significant advantage:

      • Just installed package foo, but don't really know quite how you might use it best? debian policy lets you confidently look in /usr/share/doc/foo and know that you'll find *something* that the package maintainer thought would be worth reading, even if it's only the changelog.
      • package doesn't have a man page? thanks to policy, that's an actual bug, not just an inconvenience.
      • need to understand exactly how service foo starts and stops? you can read /etc/init.d/foo
      • where are the config files? you can find them in /etc/foo/
      • and so on...

      djb is right that cross-platform incompatibility is a significant hassle. But what's his solution to that? He invents a whole new filesystem standard (see "Filesystem layout" on this page)! I respect the man for his technical prowess. And i'll grant that his proposed scheme probably makes more technical sense than the FHS, when viewed in isolation.

      But you don't achieve cross-platform compatibility through technical rigor. You achieve it through compromise, social and political consensus, transparency, legacy support, and published standards. The FHS currently represents all of those things, as does debian. In fact, that's why debian endorses, attempts to comply with, and contributes back to the FHS, because it is committed to cross-platform compatibility. djb's technical nit-picking, while usually a good thing, does him a disservice in this particular area, and debian gets it right.

    8. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 2, Interesting
      For those of us who maintain more than a handful of machines, cross-package similarity is a real and significant advantage
      You're misunderstanding me. I'm not saying Debian shouldn't add man pages, or make the documentation for package foo available under the name /usr/share/doc/foo, or generally enhance the cross-package interface of their packages. All the power to them. What I'm saying is that if, by default, openssl installs its configuration files in /usr/local/ssl, and Debian wants to put them in /usr/lib/ssl, they should support the default location by symlinking it to the Debian-specific location. That way, people can still find them at the default location. Even if they refuse to touch /usr/local, they can at least symlink /usr/ssl to /usr/lib/ssl, so all the files are in their expected locations relative to the /usr prefix. But they flat out refuse to do that because the symlink would ``clutter up /usr and violate the FHS.'' That's what annoys me.
      djb is right that cross-platform incompatibility is a significant hassle. But what's his solution to that? He invents a whole new filesystem standard
      You're misunderstanding the purpose of /package: it's not a ``solution'' to cross-platform compatibility. In fact, DJB is strictly against modifying packages downstream to fit into /package. He proposed it as a format for upstream maintainers to adopt, if they choose. Furthermore, he's made it clear what he thinks of the FHS, but he still respects the decision of upstream maintainers who have chosen the FHS for their packages interfaces. He's not telling anyone to get rid of /usr/local/bin in favor of /command; on the contrary, he suggests you symlink everything in /command into /usr/local/bin for compatibility. Please read his pages again carefully. He's terse, but his reasoning is sound.

      You couldn't be more wrong when you say Debian ``compromises'' to achieve cross-platform compatibility. In fact, they want everyone to conform to their world view; this is an uphill battle and it will never work. Different upstream authors do things differently with their packages, and they're not all going to suddenly change because Debian and the FHS are yelling at them that they're packages are ``broken.'' They choose layouts that reduce the total effort required by them to support all platforms.

      But if you're an upstream maintainer, Debian will change your package's interface downstream as they see fit and make it incompatible with your upstream version. Now all the programs which depend on your upstream interface will break on Debian. So Debian will fix those programs, too, if they happen to package them. But if they don't, your users are in for headaches.

      Don't get me wrong, Debian is a fantastic operating system. But there would be so many fewer headaches for users if they attempted to ``play nice'' with other systems, rather than saying ``It's the Debian way or the high way!''

    9. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 2, Interesting
      So they don't clutter up my /usr/local/ tree, a directory for things I've installed by hand, with automatically installed packages? Good for them. The Filesystem Hierarchy Standard says "The /usr/local hierarchy is for use by the system administrator when installing software locally. It needs to be safe from being overwritten when the system software is updated," and I'd hate to use a distribution that violated that safety.
      How, pray tell, would one measly symlink
      /usr/local/qt -> /usr/share/qt3
      violate your ``safety''? Clutter up your precious /usr/local tree? Get a grip. If you want to install a ``local'' version of Qt later, just delete the symlink and go from there.
      Why does the directory location of qt matter that much to you anyway? Fedora has it in /usr/lib/qt-3.3 and everything's working fine. In fact, I could put qt in /home/roystgnr/qt/ if I want, define QTDIR and my linker path accordingly, and unless your qt-using software is broken it should work.
      The location of Qt matters to me because, if I write a program that depends on Qt, I can provide /usr/local/qt as the default location and it will Just Work for my users. I don't have to give them extra instructions on how to find out where Qt has been installed on their system and how futz around with environment variables. Do you realize how much distributions are diluting my support resources by refusing to make packages available at their default locations? Now multiply that by the number of people writing Qt applications, and you'll see why the location matters to me.

      If you want to install Qt to a non-standard location like /home/roystgnr/qt, that's your problem to make it work. High-quality software would make the prefix of a Qt dependency easily configurable, anyways.

    10. Re:Modifying packages to conform to FHS = bad by 51mon · · Score: 2, Informative
      If the upstream Apache maintainers say Apache can be stopped with apachectl stop, Debian should damn well support this interface.

      # ps -ef | grep apa
      root 12186 1 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      www-data 12190 12186 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      www-data 12191 12186 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      www-data 12192 12186 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      www-data 12193 12186 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      www-data 12194 12186 0 19:54 pts/0 00:00:00 /usr/sbin/apache
      root 12196 10848 0 19:54 pts/0 00:00:00 grep apa
      # apachectl stop
      /usr/sbin/apachectl stop: httpd stopped
      # ps -ef | grep apa
      root 12202 10848 0 19:55 pts/0 00:00:00 grep apa

      ?

  22. Re:The best, maybe, but installation? by XMilkProject · · Score: 2, Informative

    Wish I was Debian-Guru enough to help you with all of your problems, but i'll say a few things.

    Ubuntu is basically Debian, so I don't know if I would do a clean install to switch. If your having performance problems make sure your not using the default kernel that installs, go ahead and use APT to upgrade to the 686 or K7 kernel to take advantage of your CPU. It should be very easy to do.

    What graphics card do you have that is giving you trouble? If it's ATI I can probably help.

    Regarding Gentoo, it's a very interesting way to go. It requires a bit more time and tech-savvy though. Compiling everything from scratch will yeild better performance (if you know what your doing) and Gentoo is over all a very nice distro (if you can call it a Distro). Portage is very slick. I usually reserve Gentoo for hardware that I really want to squeeze every last bit of performance out of.

    If its an ATI card your having trouble with, hit up my site (click my nick) and use the feedback form to send me an email.

    --
    Big ones, small ones, some as big as yer 'ead!
    Give 'em a twist, a flick o' the wrist...
  23. Re:Source by Mancat · · Score: 2, Funny

    I'm curious as to why you said "Wait," and then proceeded to correct yourself within your own paragraph. I mean, they call it an "edit form" for a reason. You can edit what you've typed.

    --
    hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
  24. Re:Quality control... by MacJedi · · Score: 2, Insightful
    It's much easier task to have good quality control if you only include old versions of all software. This is like cheating to me...

    You are completely wrong. The reason why Debian includes so many "old versions" of all software is because of the principle that security fixes should never force you to upgrade to the latest version; rather the fixes should be backported to the old version of the software. Thus, you don't have to worry about an upgrade breaking the functionality of your application in an unexpected way. This approach it is much harder than just tracking the current release like other distributions do with the mindset that if the software is new, too new for there to be many meaningful bug reports, then the quality must be good!

    Debian also has very stringent requirements on how many known bugs it can contain before a release can occur. Just because the software is older does not mean that it is automagically bug free. Enormous effort goes into squashing bugs, especially before a release. Don't forget that these bugs span eleven architectures too and fixing these obscure bugs which only appear on MIPS improve the software overall. I'd argue that Debian very likely does more to imporve the overall quality of Free Software than just about any other entity.

    --
    2^5
  25. Re:Debian SUCKS on SPARC --- won't install, period by Anonymous Coward · · Score: 2, Insightful

    10-15 hours to install Debian? That's too long even for an 'expert' install. Instead of wasting 20-30 hours after the first install, why didn't you just go to lists.debian.org and troubleshoot? This sounds like a troll to me.

  26. Harsh by dbcad7 · · Score: 3, Insightful
    hmmm.. A story praising Debian, you post your agreement and praise, and you are modded troll ? Is there some bad history here or is this an attempt to stop discussion of what distro each person likes ? If it is trolling to state your Distro preference, then why post stories about a distro in the first place. sheesh

    --
    waiting for ad.doubleclick.net
  27. Re:The best, maybe, but installation? by wiredlogic · · Score: 2, Informative

    Yes. A 2.6 installation kernel is available for Sarge but it isn't made very obvious. The initial root selection menu will give you a listing of the available boot images if you ask for it. I think it is INSTALL_26. I got stuck by this on my Sarge install when I ended up with a hardware incompatability under 2.4 and had to restart the whole process.

    This is important if you want to compile your own 2.6 kernel later since there a lot of 2.4 specific packages (modutils, etc.) that you won't be able to use if you don't install with 2.6 from the start.

    --
    I am becoming gerund, destroyer of verbs.
  28. Combining efforts for the greater good. by bdwoolman · · Score: 2, Informative

    I would like to congratulate Mr. Krafft for homing in on a critical issue; that is, how to maximize and focus the efforts of people working on all of these various distributions, especially the ones that are derived from Debian, to benefit a main project. As an editor I know that 90% of the work in publishing is in achieving the last 5% of perfection. To my mind, the open source movement needs to polish one beautiful gem and give it to the world. Do that and astonishing things will happen. Take Firefox for example. But it appears to my inexperienced eye that a lot of effort is being distributed across a very wide field.

    I confess that am new to the Linux world, but an old hand at computing. I successfully installed Gentoo on an old PIII as my first Linux project. I am glad I began with that difficult manual installation as I learned a tremendous amount. I did a lot of stuff with the command line, but wanted to see the GUI. Of course I could have installed a GUI environment under Gentoo, but I was curious to try something new.

    The next distribution I tried was Debian. I loved its automatic installation, especially appreciated after my experiences with Fastab, Grub, and the rest. Some irritations with the printing system aside, I was impressed by the stability and completeness and professional look this system displayed under Gnome or KDE. And the galaxy of software available is astonishing. It left me with no doubt that sooner or later open source software will leave the server farm and be the norm on the desktop, at least in some computing environments. It seems to me particularly suited to educational environments, because only open source allows students to legally take apart their tools and see how they work. But I digress.

    When I saw how many different distributions there are while doing a bit of research looking for a distribution for another old computer http://distrowatch.com/ I became concerned. Put plainly it seems to me that there are too many chiefs and not enough indians.

    Hopefully Mr. Krafft's work can harness all of this creative energy and focus some of it back into some center or other. From my limited experience the Debian distribution seems very well suited as a candidate to champion.

    --
    "No fear. No envy. No meanness." Liam Clancy
  29. Debian Annoyances by ichin4 · · Score: 2, Informative

    I've used Debian for 5+ years, not just on a desktop but also as the basis of the distributed system of a medium-sized research laboratory. I've been mostly happy, but I'm becomming restless. Yeah, apt-get is really cool, but what about...

    /etc/init.d/ scripts: Debian doesn't have a nice way to turn these scripts on and off and monitor their status via a command-line tool. Red Hat's system here was very good.

    user management: I use LDAP for user management; others use SAMBA and other stuff. But adduser isn't a shim that can interface to any of these back-end data-stores -- it can only do /etc/passwd.

    ideology: Debian's ideological bent can be a real pain for those us using the distro for its technical merits. For example, Debian pulled SSL support from all the GPL network services that link to libssl in a fit of ideology that no other distro has had.

    package management: Yeah, apt-get's dependency resolution logic is very cool. Other aspects of the system aren't so cool. Apt-get, aptitude, and other front-ends don't share the same back-end data-store, so if you mix and match these tools, you get inconsistent package data. And it's nearly impossible to force-remove a package (just delete all the damn files and forget about it!) if the associated removal script fails.

  30. Re:Countering Trusting Trust through Diverse Doubl by ObsessiveMathsFreak · · Score: 2, Insightful

    An Air Force evaluation of Multics, and Ken Thompson's famous Turing award lecture "Reflections on Trusting Trust," showed that compilers can be subverted to insert malicious Trojan horses into critical software, including themselves......This paper describes the technique, justifies it, describes how to overcome practical challenges, and demonstrates it.

    This paper is full of it.

    The technique is possible, but so impractical as to be completely useless.

    Modern compliers aren't actually that advanced. their optimisation capabilites only go so far due to their poor ability to interpret the application. As such, I seriously doubt that compiler trojans are in any way a serious threat. The threat from actual trojans in binaries if far, far, far greater.

    --
    May the Maths Be with you!
  31. Re:yeah, but you can't really search for packages by Dave2+Wickham · · Score: 2, Insightful

    So she can use Synaptic, which has pretty decent searching built in...