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

281 comments

  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 Anonymous Coward · · Score: 0

      Any info when they're going to get rid of XFree86 and put in Xorg like any other distro in the last 2 years?

    2. 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
    3. Re:Debian has always been the best by Anonymous Coward · · Score: 0

      I suggest updating your deb pkg manager i.e. synaptic or aptitude.

    4. 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..

    5. Re:Debian has always been the best by davez0r · · Score: 1
    6. Re:Debian has always been the best by Anonymous Coward · · Score: 0

      xorg has been in unstable since [2005-07-11] and in testing a bit shorter than that.

      6.9 will reach testing any day now, and the work on the modular tree (7.0) is closing in on an upload to experimental.

      happy days, and i'm quite confident you'll see 7.0 in etch when it releases in 11 months.

    7. Re:Debian has always been the best by ChefInnocent · · Score: 1

      I've used Debian before. It was ok until it was hacked. Although it did seem to be a bit more secure than RedHat and Fedora. Now though I'm solidly an OpenBSD guy. Sure it's a pain in the ass to use, but it is secure damn it, and it is pretty easy to know what each and every process is since nothing is started by default.
      What is the deal with RedHat/Fedora starting so many freaking processes? I don't want to spend a month doing a man on each one trying to memorize them all. I've got other things to do with my time than be a SysAdmin.

    8. Re:Debian has always been the best by Anonymous Coward · · Score: 0

      I don't know what debian your' looking at. My experience is otherwise. I guess that might be because when I think of 'easy' to use that my expectations are different. For example pkg_add -r mozilla-firefox works. As is hwd -xa and having a working xorg conf. I tried hwd on debian didn't work, odly lshwd did. Again I guess my expectations are different. I would like to know from you, or anyone else, is this: Is their a reason why so many people who use Debian need to cary their feelings in their hands, and their polotics on their shirt like a badge of honor? It's a major turn off when considering Debian again.

    9. Re:Debian has always been the best by Anonymous Coward · · Score: 0

      running xorg7RC on my dapper.

    10. Re:Debian has always been the best by ryanov · · Score: 1

      I love a joke I saw that was in the style of the demotivational posters.

      Slackware -- the very best 1995 has to offer (with a picture of Win 3.11 TCP/IP config on the screen).

    11. Re:Debian has always been the best by cg0def · · Score: 1

      First Ubuntu/Kubuntu is NOT debian and worst of all DOES NOT follow the debian ideas. The only thing that Ubuntu and Debian have in common is the technology. Ubuntu and Debian don't even feel the same so don't even get me started on how disappointed I am with what Ubuntu has done with Debian. As far as updates go ... well I'd admit that certain things in debian take and awful long time to be admited to even the testing branch ( firefox 1.5 for one ). However, the stable branch is designed for maximum security which usually means servers and such and when you are talking about security that means that every package accepted has good through a lot of testing and has been found safe ( as far as the developers know ). There are also 3 other branches ( testing, unstable, experimental ) and if you want bleeding edge with decent stability you can always try unstable. Yes some of the packages are a little bit older that those in ubuntu but man the whole OS feels so much better plus if I don't wan't gnome I don't have to install it and the same goes for pretty much everything else. Oh yeah and last I checked there was still no net install CD for Ubuntu. I appreciate the free CDs that Ubuntu sends but I still think that forking Debian was about the dumbest thing that they could have done. It also doesn't help the linux community at all. But that's just me. As far as Debian goes, it's a lot easier that some people have come to believe it to be.

    12. Re:Debian has always been the best by Anonymous Coward · · Score: 0

      Why don't you use the real X7 release? It's been out for a while now, does Debian not have a package yet? Even Gentoo has had it available for over a month.

  2. Timeline in perspective by SilverspurG · · Score: 1, Insightful

    Hmmmm... started using Slackware around '95, went through a few kernel revisions, then put computers on the back-burner for a while to investigate post-puberty options. So how old did that make him during his long time NT testing years? How do I sign my kids up for that sort of opportunity at age 11-13? Maybe there's a reason why "Microsoft had ignored every single one of my elaborate suggestions and wishlist reports in 4.0".

    I'm sure he makes many important contributions but, wow, people tell me that I'm arrogant if I make an elaborate suggestion at 30.

    --
    fast as fast can be. you'll never catch me.
    1. 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
    2. Re:Timeline in perspective by SilverspurG · · Score: 1

      Very nice. :) I admire your good luck.

      --
      fast as fast can be. you'll never catch me.
    3. Re:Timeline in perspective by Anonymous Coward · · Score: 0

      Not trying to be rude, but "you're too arrogant for your age" is probably a nice way of saying that your ideas suck ;)

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

    ...RTFM !!

    Ah, it is still good though.

    1. Re:Debian in a Nutshell... by vga_init · · Score: 1
      I realize that your post is intended to be a joke, but my first reaction upon seeing this article was something akin to, "What? 'Debian System Explained'? Doesn't Debian explain itself?"

      I have recently switched to Debian-based (Ubuntu on the desktop now, ran Sarge prior to that for several months). The system documentation is quite detailed and exhaustive. Also, it's not just for the expert user--the system is clear enough for even casual users to get a handle on quickly.

      Debian speaks for itself and is consistent. Surprisingly, I've haven't felt this way since I used FreeBSD (whose documentation is astoundingly good, I might add).

  4. 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 Anonymous Coward · · Score: 1, Interesting

      Sarge is a dream, but the situation trying to run media-rich apps on it is a nightmare.

      Wanna build MythTV on the just-recently-stable (recently on the Debian timescale anyway) Sarge? Sorry - about a week after Sarge went stable, MythTV moved up to the latest unstable. That's just one example - there are others. Miserable situation.

      What good is a stable OS release if people won't build the apps for it?

    3. Re:All I know is... by daliman · · Score: 1

      Printer control simple? What are you using? I find printer control under Linux a complete PITA on all distributions. I generally solve this by not printing anything out at all if possible :)

    4. 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
    5. 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
    6. Re:All I know is... by 6*7 · · Score: 1

      If you want cutting edge Debian/stable is not for you. Debian/unstable might be.

      I guess this is in TFA somewhere but stable/unstable in the name has no relation to the stability of the running machines/processes. It reflects the versioning of installed software.

      IMHO:
      -stable: mainly on servers (trying not to have to roll your own (updated) packages) and corporate desktops.
      -unstable: user desktop (reminder: sometimes software/packages are broken, test when mission critical before updating)
      -testing: anything inbetween

    7. Re:All I know is... by buchanmilne · · Score: 1

      Compared to:

      -printerdrake (if Mandriva installation didn't find your printer - ie network printer or similar), which you can run from the Mandriva Control Center
      -system-config-printer (RedHat/Fedora)
      -(I guess SUSE has something similar in yast2)

      Sorry, but having to know the 4 packages you need to install, then manually choose the backend (or figure out the foomatic command-line necessary) doesn't qualify as "easy".

    8. Re:All I know is... by ryanov · · Score: 1

      I'll agree to that. If I want to do something other than standard stuff that's in the respository, you're going to run into trouble. But when Kubuntu came along, I did install it on my laptop and it's working out just great.

    9. 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.

    10. Re:All I know is... by ObsessiveMathsFreak · · Score: 1

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

      What's apt-get?
      What's cupsys?
      What's cupsys-driver-gimpprint?
      What's cupsys-client?
      What's cupsys-pt?

      And most importantly.... ...why do I need to know all of this stuff just to get the printer working in Debian?

      --
      May the Maths Be with you!
    11. Re:All I know is... by daliman · · Score: 1

      The problem is the drivers, normally :) You have the same setup I do. However, cups is hardly unique to Debian...

    12. Re:All I know is... by zoloto · · Score: 1

      Holy shit that works in OS X.
      I tried my user account password but nothing works.
      Hot damn, that was a good little discovery on my new OS X iBook

      *shakes head in disbelief*

    13. Re:All I know is... by cortana · · Score: 1

      > What's apt-get?

      http://debian.org/doc/

      > What's cupsys?

      apt-cache show cupsys

      > What's cupsys-driver-gimpprint?

      apt-cache show cupsys-driver-gimpprint

      > What's cupsys-client?

      apt-cache show cupsys-client

      > What's cupsys-pt?

      apt-cache show cupsys-pt

      > And most importantly.... ...why do I need to know all of this
      > stuff just to get the printer working in Debian?

      Ah, you're a desktop user. Pick 'desktop' when prompted while installing and I believe all this stuff will be installed automatically. You can then go to Desktop -> Administration -> Printing to add your printer.

    14. Re:All I know is... by ObsessiveMathsFreak · · Score: 1

      This is why Ubuntu is the new number one distro. The Debian kids just don't get it. Even Fedora has a (poor) graphical installer.

      --
      May the Maths Be with you!
    15. Re:All I know is... by cortana · · Score: 1

      FYI, Debian and Ubuntu use the same installer.

  5. 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.

    1. Re:As interesting as the technology by illustir · · Score: 1
      Our faculty of management at Delft, University of Technology is actually doing this.

      A teacher of mine Ruben van Wendel de Joode has recently got a Ph.D. on organizational aspects of Open Source Communities.

      --
      -- Alper
  6. Re:oblig 2nd post by Anonymous Coward · · Score: 0

    exept ... you didn't

  7. 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 MacJedi · · Score: 1, Insightful
      As time -> Infinity, Linux -> Debian

      (-:

      --
      2^5
    2. Re:Is Debian a fad? by ChefInnocent · · Score: 1

      That isn't to dissimilar from my path. SuSe, Red Hat, Debian, OpenBSD. I tried Fedcora on an alternate server, but when back to OpenBSD. I like knowing what my OS is doing, and I like that nothing is started without my explicit say so.

    3. 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.
    4. Re:Is Debian a fad? by clydemaxwell · · Score: 1

      mandrake, red hat, red hat, debian :p Though I use SuSe at work.

      --
      Browsing with classic discussion, noscript, at -1 and nested
      no hidden comments and I only mod UP
    5. Re:Is Debian a fad? by kaens · · Score: 1

      Huh. I went Ubuntu -> LFS.

    6. Re:Is Debian a fad? by Anonymous Coward · · Score: 0

      If you're going to take the time to build a LFS box, you might as well use Gentoo. Same built from scratch feeling, but a hell of a lot easier to build.

    7. Re:Is Debian a fad? by Theatetus · · Score: 1

      It's interesting how much people's distro path depends on when they started. I installed my first Linux (RedHat... 6 I think) in '99. Then Suse in '01, then OpenBSD in '02, and since '03 alternating between that and Gentoo based on whichever one supports whatever piece of hardware is giving me trouble.

      Though I've never used Debian (apart from at work) I do appreciate its existence. I see Debian as sort of a Reference Implementation of GNU/Linux (that may well have been their goal, for all I know). I also may be the only person who *won't* complain about how long it takes packages to get included in the ports tree (or whatever apt calls it). "Stable" is called "stable" for a reason (and has nothing to do with what most people think): the applications in a stable platform do not significantly change until a complete version upgrade.

      Plus, some of the management tools developed by the Debian team are great. Common-lisp-controller is just beautiful.

      --
      All's true that is mistrusted
  8. 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 outsider007 · · Score: 1

      For me it's all about will I be able to build my tarballs without jumping through a million hoops. Other than that all distros are the same to me. Not really sure how Debian stacks up against RH enterprise in this but I know that oracle 10g won't even go on Debian so right off the bat they lose being my db server, and why not keep everything simple by using the same distro for everything I do?

      --
      If you mod me down the terrorists will have won
    4. Re:Other Distros by Anonymous Coward · · Score: 0

      Most serious linux administrators that aren't running Red Hat, don't have a gui installed on their servers.

      There simply isn't a need.

    5. Re:Other Distros by kotj.mf · · Score: 1

      Though I've never tried installing the server, I _have_ successfully faked out the Oracle 10 client installer on Sarge by adding an /etc/version* file. Though if you actually need support from Oracle, it's probably not a good idea.

      *I can't remember exactly what it is at the moment... whatever Redhat uses. If you really wanna know, I can take a look at work tomorrow.

      --
      hang brain.
    6. Re:Other Distros by synthespian · · Score: 1

      Well-tested, stable packages with no dependency issues or known security bugs

      Hahaha...Don't lie.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    7. 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.

    8. Re:Other Distros by stevey · · Score: 1

      I'm a Debian developer and system administrator and I love using Debian in production environments. It is definitely an enterprise-ready distribution (whatever that really means.)

      Having said that there are times when I can't use it, much as it pains me. For example today I'm installing SuSE enterprise server on a new box for a client - they demand this so they can get Oracle support. (Even though in practise this will never be needed.)

      There are a lot of Debian System Administrators who are happy with Debian in large environments.

      Of course I'm biased since I look after a sysadminish Debian site..

    9. Re:Other Distros by 51mon · · Score: 1
      Is Debian that much better whe it comes for day to day operations?

      Stevey lacks enough karma so I'll reply as well ;)

      Yes. Assuming by day to day operations you mean installing and configuring software, which is what system admins tend to do.

      Oh you wanted a longer response? Debian is very easy to manage because the packages fit and work well together. If you want "Postfix" with a "postgres" backend for authentication, you type "apt-get install postfix-pgsql" (or use a GUI if you must), the packaging tools figure out the dependencies. The Postgres server isn't a dependency, as the database might be on another server, but replacing your current incompatible MTA (usually Exim) would be an action performed, if necessary, after it asks if you are sure about the derived changes it wants to make.

      Most other distros would expect you to remove the existing MTA yourself, and probably don't have a prebuilt package for this (admittedly fairly unusual) task, and you'd probably have to build Postfix, or a package for Postfix, from source, with some arcane './configure --with-pgsql --with-ssl --with-losing-will-to-use-free-software --with-wondering-why-we-didn't-buy-exchange' options.

      Superficially this looks like a good packaging system, but the submerged iceberg mentioned in the article is 16,000 packages almost universally high quality packages that make this possible. For every MTA to replace the old MTA the package must declare it is an MTA etc etc.

      Generally these packages are standard free software packages, but the Debian developers will make little changes to make them consistent and flexible. For example Postgres comes with a slightly tightened security set up as the source built one is rather insecure for most hosting environment. I dare say a lot of servers are just those little bit better configured for those little touches to the postgres security config. That consistency includes something in /usr/share/doc/packagename that at worst will include a URL to the documentation, and a file explaining any Debian customisations or perculiarities.

      Even where Debian does push you out to compiling stuff from source (and you can build some pretty crazy and complex systems without going to source), the packaging system makes it easy to pull in the tools to do it. Need a new kernel, a package exists to help you make kernel packages easily from source, and Debian also provides kernel source packages with little customisations already applied.

      I've no doubt Redhat has improved immensely in these areas since the versions we have, but the selling point with Redhat is the commercial support, and standard platform nature for certain applications. For certain enterprise applications, like Oracle, running outside the vendor supported platform is a no-no. So you have to buy a standard platform. Almost all big commercial applications support Redhat, most will run on Debian, but if your paying big money for applications the bosses expect proper vendor support and so it is Redhat. The ISP business is more flexible generally in these areas, and Debian is huge in this area.

      My main gripe with the article, is I'd happily recommend Debian for the beginner. I wouldn't recommend they install it themselves, or configure it themselves, but if a relative wants a computer to surf and email, and print, and you want to set something up and forget about it, and yet still be able to install new software remotely with ease and speed.

  9. Easy Install... NO install!! by helmutvs · · Score: 1, Interesting

    Knoppix is the best tool with which to showcase Debian-based systems. No installation/configuration required. Along with Ubuntu, it is quite possibly the easiest-to-use linux out there.

    --
    There are no uninteresting things. There are only uninterested people.
    1. Re:Easy Install... NO install!! by Anonymous Coward · · Score: 0

      I'd have to agree. My first experience with Linux was Knoppix. I did the hd install (basically Debian) on my laptop after checking it out. I had a few problems with it, which is not surprising for a total Linux n00b installing it for the first time and dropped it after about 2 months. After that I checked out a few of the rpm based distros but they didn't even last that long. Even though I was still a *total* n00b, I knew the .deb system was for me.

      Then I found Ubuntu.

      Even though I'm still a n00b, I've gotten alot more used to Linux and I friggin love it. Sure, there were a few hiccups but nothing a quick search of the Ubuntu forums didn't easily solve. I've even gotten used to compiling things from source (even though most of the time I don't have to), doing some things from the CL (not all, yet), configuring my system just the way I like it, etc. I can safely say that Ubuntu (or another Debian distro) will be my main OS for the rest of my life. I have seen the light!

      Thank you, Ubuntu!

  10. Flame on! by Anonymous Coward · · Score: 0

    From TFA:
    "And because everything is designed with little pieces building on top of each other, it's easy to keep an overview. This directly translates into manageability and security. In other words, you control the system, and not the other way around."

    In Redmond, Washington the system controls YOU.

    Now excuse me while I get my asbestos suit.

  11. 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!

    1. Re:Shhhhhhhh!! by advocate_one · · Score: 1
      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.

      well, if you think Debian is getting too mainstream, there's always the wild wooly frontiers of something like Plan 9...

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    2. Re:Shhhhhhhh!! by i_should_be_working · · Score: 1

      "well, if you think Debian is getting too mainstream, there's always the wild wooly frontiers of something like Plan 9..."

      Or Debian Hurd.

    3. Re:Shhhhhhhh!! by Hosiah · · Score: 1

      You sound like an Ozzy fan. Lived through the 80's being reviled and disdained as a Satanist and druggie and wierdo because he listened to Black Sabbath, only to approach middle age and find out Ozzy's an MTV reality show. Teens coming up to him: "Seen the Osbornes?" "No, but I followed Ozzy back when he was with Black Sabbath." "Black who?"

    4. Re:Shhhhhhhh!! by Anonymous Coward · · Score: 0

      VERY TRUE! averything is going down.

      And Google will eat us all.. while making money out of it.

    5. Re:Shhhhhhhh!! by level_headed_midwest · · Score: 1

      You could always write your own distro. Do it in assembly language- that would certainly be unique.

      --
      Just "gittin-r-done," day after day.
    6. Re:Shhhhhhhh!! by BrainInAJar · · Score: 1

      You could always use slackware.

      or gentoo...

    7. Re:Shhhhhhhh!! by cfx666 · · Score: 1
      I could explain you why your "nerdity by obscurity" concept is not working at all. But this is l33t wizdom and 1 c4n n01 r15k t0 l0053 mY 1337 p0w3z...

      Cfx

      --
      You have 2 nucular Moderator Points! Use 'em or loose 'em!
    8. Re:Shhhhhhhh!! by Anonymous Coward · · Score: 0

      I'm impressed - you went through the effort required to translate into l33t, and still managed to mess up lose/loose.

    9. Re:Shhhhhhhh!! by Andrewkov · · Score: 1

      Including spelling..

    10. Re:Shhhhhhhh!! by Anonymous Coward · · Score: 0

      Hello
      The parent is *Insightful* and not Funny.(Frown) That is exactly what I feel. Infact I leave things when they become popular!

  12. Debian SUCKS on SPARC --- won't install, period by Infosec+Geek · · Score: 0, Troll

    It really is too bad that Martin Krafft fails to explain how to install the SPARC port of Debian. The last time I tried this, I had dug through the relevant portion of his book, and had it open next to me.

    His description went wide of the mark quite quickly, and became totally useless shortly thereafter.

    The install failed, of course. The OS went in, but the system went into spin-lock upon bootup attempt. That was about the third staight install failure for Debian 3.0r1 SPARC (each one burning 10 to 15 hours of my time), and it was the one which finally snapped my patience.

    The SPARC32 gear of a dozen years ago was put together quite well, even if it isn't nearly as speedy as recent Intel kit. Even after the processors have been changed out for faster aftermarket Ross Hypersparcs.

    Too bad that no Linux distro has supported it for half a decade. Yeah, catcalls, mudgobs, and rotting veggies also go out to RedRat, SuSE, and Mandrake.

    And it's really too bad that Debian wastes our bloody time by pretending to support SPARC hardware.

    I'm waiting for the first "BSD is dead" troll to show up. I can really use the bellylaugh. Because installing OpenBSD/SPARC32 on one of those old systems is a complete slam-dunk. Stock processors or Hypersparcs, single-proc or dual.

    1. Re:Debian SUCKS on SPARC --- won't install, period by slashdotnickname · · Score: 1

      I'm waiting for the first "BSD is dead" troll to show up.

      BSD is alive

      learn how to install stuff, you noob

    2. Re:Debian SUCKS on SPARC --- won't install, period by selfabuse · · Score: 1

      That's odd - I've had very good luck with Debian on Sparc. Perhaps I was using older hardware then you were. I've installed Debian with no issues on an old Sun Pizza Box (SparcStation II, maybe?) and a bunch of IPCs. I even had the IPCs netbooting debian off a NetBSD box for a while. This was all on Woody. The only problem I had was getting fdisk to do the Sun disk labels properly. I don't know anything about Mr. Kraffts books, but I found a quick howto via google, and it was right on the money.

    3. 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 --> .
    4. 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
    5. Re:Debian SUCKS on SPARC --- won't install, period by Infosec+Geek · · Score: 1

      I did my first install on a Sun box in 1988. Not Solaris. SunOS. Piece of cake. But it took FOREVER to spool the OS distro off that QUIC-24 tape drive.

      And of course, BSD is alive. Furthermore, as I hinted earlier, it's dead easy to install on SPARCs.

    6. 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
    7. Re:Debian SUCKS on SPARC --- won't install, period by Infosec+Geek · · Score: 1

      Yeah, it's the kernel that bites. Getting the distro on is pretty easy. Booting, on the other hand .... I draw a merciful veil.

    8. Re:Debian SUCKS on SPARC --- won't install, period by dotgain · · Score: 1
      No problems at all installing Deb 30_r1 on Sparc sun4m SparcStation20, two CPUs and rather uncommon cgfourteen framebuffer.

      Excuse me?

      Distros I've had success with in the last two years on a Sparc32:

      • Gentoo (but don't waste your time)
      • Debian (of course)
      • NetBSD (okay, it's not Linux, but it is a distribution)
      • and a very old (so don't count it) Mandrake release
      I won't call you troll, and agree, some of the docs do miss the mark badly, but it is you that failed, not Debian.
    9. 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
    10. Re:Debian SUCKS on SPARC --- won't install, period by GammaTau · · Score: 1

      As far as I know, the problems with Linux on sparc32 are bit rot and other problems in the Linux kernel code. Debian, SuSE and Mandrake are Linux distributions and they distribute software written by others. No distribution has full support of sparc32 hardware because sparc32 issues are not distro issues. They are issues with kernel development, and especially lack of interest from kernel developers.

    11. Re:Debian SUCKS on SPARC --- won't install, period by BrookHarty · · Score: 1

      The latest debian netboot works great, it detected hardware on some ultra 10s and blade 100s. Now 3.0 didnt work, but 3.1r did perfectly. Maybe you where using an older netboot, time to upgrade.

    12. Re:Debian SUCKS on SPARC --- won't install, period by Chaoticmass · · Score: 1

      First time I ever *successfully* installed linux it was a Debain Sarge netboot install on a Sun SparcStation LX. It worked so smoothly it really made a strong impression on me and now Debian is my favorite linux distro. In my experience Debian netinst is about the most painless way to get linux on a computer.

      I've only tried Fedora Core 3, Mandrake 10, and NetBSD so my experience is limited, but Debian has worked the best for me. I've installed it on new home-built PCs, a Thinkpad T23, and old old Thinkpad 701C, older desktop machines, and the previously mentioned SparcStation LX.

      Debian is not the best distro for every niche, but it's flexible enough to work well in many different situations.

    13. Re:Debian SUCKS on SPARC --- won't install, period by Mancat · · Score: 1

      Or you can use NetBSD, from which OpenBSD is taking all of its SPARC SMP code. 'Cause it actually works.

      --
      hello dear sirs my name is jamesh i are india (bihar) can u guide me install red had linux 9?
    14. 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.

    15. Re:Debian SUCKS on SPARC --- won't install, period by Anonymous Coward · · Score: 0

      I've had trouble getting fdisk working as well. It would not utilize the whole drive and limit the max cylinders of my new disk to 65536. I was able to use parted and sfdisk instead without problem. This was on the newest release of aurora sparc linux.

    16. Re:Debian SUCKS on SPARC --- won't install, period by cortana · · Score: 1

      Did you fill in an installation report, or even mail in a bug report?

    17. Re:Debian SUCKS on SPARC --- won't install, period by BrainInAJar · · Score: 1

      Now try it on an ultrasparc.

      After trying it 4 times, I FINALLY got a kernel compiled on my ultra/2. on bootup, it gave me panics.

      After that, i was so fed up I downloaded an opensolaris CD.

    18. Re:Debian SUCKS on SPARC --- won't install, period by m50d · · Score: 1

      I don't have one but my friend does. It's working fine (pings)...yep, it's working fine.

      --
      I am trolling
    19. Re:Debian SUCKS on SPARC --- won't install, period by kan0r · · Score: 1

      The Debian SPARC port surely has some issues. It is also not yet officially qualified for Etch.At the moment it doesn't look good. But chances are that it'll make it into the next release. If everyone only complains instead of helping to set the SPARC port back on his feed, its going to take a lot longer.. ;)

    20. Re:Debian SUCKS on SPARC --- won't install, period by phusg · · Score: 1

      Good in theory, but when I did just that with the problem I had installing sarge on a Sun UltraSPARC 1E but no-one ever replied! See my report here: http://lists.debian.org/debian-boot/2005/04/msg008 27.html If anyone can give me a pointer I'd be really grateful, I still have the machine gathering dust at home.

  13. 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'...
    3. Re:Huh? by Anonymous Coward · · Score: 0

      Whatever.

      Unstable may 'be out of date', but it's damn sight newer in most ways then Ubuntu.

      Sure it used Xfree86 for a long time, but if most people had a clue they'd realise that XFree86 that shipped with Sarge is more X.org then anything else. It was kept at the XFree86 versioning for compatability reasons. Go check it out, it supports hardware and features that the latest Free version of Xfree never supported. That is the sort of thing you get when more then a couple X.org developers are also Debian Developers.

      Right now I am using X.org 6.9 with my Debian desktop.

      A 'scalable OS' means that it's actually _scalable_ not that it has the latest and greatest of everything.

      Right now Debian has 17,000 or so packages. This is _officially_ supported software with bug reports, security updates, and more accountability. No other Linux distro does this. Not even Ubuntu.

      Sure Ubuntu has supported software in it's 'main' and sure it has a stale-ish snapshot of Debian Sid for it's Univers e and Multiverse software, but only the small subset of packages is going to be officially supported. For everything else your pretty much on your own.

      This is not to say Debian is perfect, or Ubuntu sucks. Far from it. I wouldn't wish Debian Unstable on my worst enemy if they weren't already familar and comfortable with Debian. And Debian Stable is cronicly out of date.

      But there are several reasons I use Debian personally..
      (in no paticular order)
      1. For Debian Stable updates are fairly low volume. This makes it easy to run servers on a long term basis and with little maintainance.
      2. For Debian Unstable it's always a rolling update. That way problems occure in small ways over time.. rather then in big disruptive updates like with other Distros.
      3. A crapload of supported software.
      4. Quality control is the most important thing that I like about it. This is the most serious quality that is lacking from most other distros. It's unfortunate. Probably the major exception is Slackware.

    4. Re:Huh? by IamTheRealMike · · Score: 1
      Well, so far two people have said "scalability does not mean what you think it means". So what does it mean, in this context? Seems like it could mean many things - I interpret a scalable distro to mean a project that scales well as it grows in utility and number of people developing/using it. And Debian doesn't seem to scale - as they add more packages, it becomes harder and harder to do releases. Actually that's true of all distros but most of them have "solved" it by only making guarantees about a small core set. Not really a solution at all IMHO.

      And as to Longhorn, well, you could argue that this project hasn't scaled management-wise ... true. But so what? Does Debian really want to compare itself to the next version of Windows in the sense of "well we're not quite as bad as that"? Bear in mind Debian merely integrates, if you look at the amount of code actually produced by the Debian project it's quite small relative to Red Hat, and tiny relative to the Vista team.

    5. Re:Huh? by BeeRockxs · · Score: 1

      What does scalability have to do with speed of releases?
      What does robustness have to do with how many people do the security updates?

    6. Re:Huh? by MacJedi · · Score: 1
      I interpret a scalable distro to mean a project that scales well as it grows in utility and number of people developing/using it.

      A more apt interpretation might be something like, "a distro which can be installed on everything from small embedded systems to large NUMA machines with minimal hassle" or "a distro which which can install on eleven (11) architectures using the same installer and with virtually all packages installable on each."

      --
      2^5
    7. Re:Huh? by Idealius · · Score: 1

      I was going to rate this up, then realized there is no +Pun.

      +Pun on use of the word 'apt'. Have a nice day.

    8. Re:Huh? by bcrowell · · Score: 1
      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).
      I like Debian because it's free as in beer. Seriously. You mention Red Hat as an alternative, but Red Hat is really oriented toward people who are willing to pay for various services associated with the OS. I'm not aware of any noncommercial Linux or BSD system that's anywhere near as solid and easy to use as Debian & co.

      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 ...
      They're not forks. They're different releases based on essentially the same codebase. Code flows back and forth between Ubuntu and generic Debian. I run Ubuntu on my desktop machines, but actually running Ubuntu has made me more appreciative of vanilla Debian's conservative approach. The last two releases of Ubuntu have both shipped with what were, for me at least, pretty serious problems. (The current Ubuntu ships with a version of the GTK2+ libraries that breaks all Perl/Tk apps by crashing them when they're run alongside of GTK2+ apps. Ouch!)

    9. Re:Huh? by Hercynium · · Score: 1

      Golf clap for you sir!

      That was a fine, fine troll there. You managed to *sound* knowledgeable, intelligent, and empassioned without being crude and obvious! You even worked up some righteous indignation to cover for your logical errors. You are truly a professional in your field...

      which is obviously not systems administration, development, design, or support.

      And, if that wasn't a troll... I suggest you get yourself some warm milk and a blanket, and boot back into Windows XP.

      --
      I'm done with sigs. Sigs are lame.
  14. yeah, but you can't really search for packages by rsilvergun · · Score: 1, Troll

    I really miss swaret --search when I'm in ubuntu on my friends pc. It's a major pain having to know the exact name of a package.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
    1. Re:yeah, but you can't really search for packages by Anonymous Coward · · Score: 0

      apt-cache search

      You do not need to know the entire package name.

    2. Re:yeah, but you can't really search for packages by Anonymous Coward · · Score: 0

      Really? Have you tried "apt-cache search "?

    3. Re:yeah, but you can't really search for packages by rbochan · · Score: 1

      Browse through this, it's well worth the read.

      --
      ...Rob
      The American Dream isn't an SUV and a house in the suburbs; it's Don't Tread On Me.
    4. Re:yeah, but you can't really search for packages by Anonymous Coward · · Score: 0

      The command you're looking for is probably:

      apt-cache search [keyword]

    5. Re:yeah, but you can't really search for packages by sameeer · · Score: 1

      on ubuntu, u can also use the search search (including names and description) in the synaptics package manager..

    6. Re:yeah, but you can't really search for packages by XMilkProject · · Score: 1

      apt-cache search wookie

      --
      Big ones, small ones, some as big as yer 'ead!
      Give 'em a twist, a flick o' the wrist...
    7. 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.
    8. Re:yeah, but you can't really search for packages by ObsessiveMathsFreak · · Score: 0, Flamebait

      I have an alias set up that allows searching from the command line quite easily ....
      Then, to look for something like... libvorbis, I would just have to do this: ...
      And it returns this: ....
      Easy as pie.


      That was easy as ABC! I'm sure my Aunt Tillie can figure this one out all by herself.

      --
      May the Maths Be with you!
    9. 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...

    10. Re:yeah, but you can't really search for packages by ichimunki · · Score: 1

      So do you recommend for Aunt Tillie instead of Debian?

      --
      I do not have a signature
    11. Re:yeah, but you can't really search for packages by ObsessiveMathsFreak · · Score: 1

      So do you recommend for Aunt Tillie instead of Debian?

      TiVo.

      --
      May the Maths Be with you!
  15. 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 fimbulvetr · · Score: 1

      I haven't purchased or even bought TFB, but there are some things I wonder:

      1. Is apache 2's layout covered? I understand it, because it's intuitive to me because I've been working with huge numbers of virtual hosts for years, but many of my friends/coworkers get confused by the whole sites-enabled/sites-available thing.

      2. Is it covered that apache and apache2 can coexist and the gotchas of such a setup?

      3. Do you cover the areas where sysadmins can get bitten? For instance, if I have hundreds of gigs and millions of files in my /home directory, do you mention that it's a good idea disable the cron that searches every night for setuid files, etc, otherwise the load will kill the machine?

      4. Do you go into the updating suggestions? For instance, is it a good idea to run apt-get update; apt-get upgrade in a cron? If not, do you suggest we log in everyday and do it? Or is there a utility you include in your book that can list the updates available for that specific machine and email it to an admin everday? How about reporting it to something like hobbit?

      I could go on...and on...but I'm anxious to hear your responses.

    3. 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
  16. 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 Anonymous Coward · · Score: 0

      Uh, you didn't specify which distro you dumped Debian for. Everybody's waiting, man.

    2. 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
    3. 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.

    4. Re:Great book, too bad about the software by DocLandolt · · Score: 1

      What is this magic distro you speak of? ...I'm a noob who's been pimping an ubuntu distro for about a month -- and I'm really not as happy as I thought I'd be. In many ways I LOVE linux and what it's offering me (like endless fun with tweaking), but ultimately, it's not all it's cracked up to me. I've grown weary of Microsoft, and really wanted to switch full time -- but I find myself back in the dual boot of XP almost daily -- just so I can 'get things done'.

    5. 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
    6. Re:Great book, too bad about the software by Anonymous Coward · · Score: 0

      Depends on what "Just get things done" means. Office work, programming, servers, it's just a matter of running synaptic or aptitude(pick one, probably aptitude, and don't use the other commands as aptitude will not track other update programs) and finding the right program. I would use Debian testing/unstable as my main desktop, but I run too many games.

    7. Re:Great book, too bad about the software by poopdeville · · Score: 1

      IME, you have to fiddle very little with any of Debian's tracks. Sure, you might need to mess around in /etc to configure a package to fit your particular needs, but Debian packages are usually configured with sane defaults. They tend to work for most uses right out of the 'box'. Server packages like Apache and Samba tend to be exceptions -- the defaults are still sane, but you realistically should expect to have to configure a server to fit your needs.

      --
      After all, I am strangely colored.
    8. Re:Great book, too bad about the software by synthespian · · Score: 1

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

      The very fact that a Debian developer has written a book on how the Debian "System" works shows, in a very clear way, that the project has terrible documentation.

      They have what amount to rough drafts. Disorganized and out of sync with the system. Nothing like the FreeBSD handbook, or the OpenBSD man pages (Linux man pages are the antithesis of Unix man pages.) In OpenBSD's case, a man page update is mandatory when the software is patched and has functionality altered (this wasn't always so, but they developed that culture).

      Alas, I'll have to buy it. Let's hope this time things are explained clearly.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    9. 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ï
    10. Re:Great book, too bad about the software by chthon · · Score: 1

      Just what is it that you need to do ?

      I have put my father on Linux fulltime, and my wife uses it too on my terminal server.

      I have written a introductory and an advanced course on Linux, but it would be nice to have some input from someone who normally uses Windows and now tries to switch.

    11. Re:Great book, too bad about the software by sammy+baby · · Score: 1
      No offense, because I can understand where you're coming from, but surely you can see the flaw in your own reasoning.

      I was sick and tired of my old doctor. He was always telling me what to do. So I got a new doctor. The first day I went into the office, I picked up his reflex hammer and started trying to put it up my nose. "Hey, dude," my new doctor said. "Quit that, you're gonna hurt yourself."

      "Dammit, Doc!" I said. "Can't you see that I only came here in the first place because I don't want you telling me what to do!"


      Translation: if you want it to be stable and easy, and you go with branches labled "testing" and "unstable," you kinda forfeit the right to complain later, regardless of how well you take constructive criticism.

      (For a later conversation: semantic differences between "endless fiddling around and careful management" and "mucho tweaked.")
    12. Re:Great book, too bad about the software by tenco · · Score: 1
      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 used Debian for over two years. In the end i was always running unstable, because the stable packages were simply to old. As you might know, to keep unstable up to date requires ~200MB to download a week (because an update of a tiny library can generate a huge download of all packages which depend on that lib). I finally switched to Ubuntu because it has support for madwifi.

      Now i am running Dapper (Ubuntu 6.10) for mainly two reasons: tetex-3 (improvements in pdflatex) and xorg-7.0 (DRI-support for prosavage8 videocards).

      I would love to run Debian vanilla again on my machine, but i simply cannot wait your "fast" 18-month (1.5 years!) release-cycle.

    13. Re:Great book, too bad about the software by joeytsai · · Score: 1
      Debian was too demanding of time and needed seemingly endless fiddling around and careful management.

      To answer another reply, I now use a mucho tweaked SuSE.

      So, do you like tweaking or not?
      --
      http://www.talknerdy.org
    14. Re:Great book, too bad about the software by Anonymous Coward · · Score: 0

      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.

      Either you didn't understand it, or you got it mixed up with another OS.
    15. 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ï
    16. Re:Great book, too bad about the software by Anonymous Coward · · Score: 0

      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.

      This is a perfect example of not understanding users.

      With Debian releases so far apart, "stable" really means "old". And "old" means (a) can't find current versions of apps I want, and (b) more twiddling needed. For better or worse, lots of Debian software is undergoing rapid development, so (a) means it's often difficult to get documentation or support for apps in "stable". And look at each new Gnome release, and how much more in the way of administration tools they add -- (b) is because old versions of Debian were simply harder to use.

      So it's not simply a choice between "stable" and "unstable". It's a choice between "unstable = packages might not work 100% today", and "old = apps are ancient, and you need to do more geek-work by hand". Given that choice, it's not hard to see why most people will pick "unstable" for their personal workstations.

      I've run Debian for close to 10 years, and I have no plans to change. However, supporting normal users is not one of their strengths. The way the whole "stable/unstable" system is run is evidence of that. Apple has nothing to fear from Debian, for at least several years.

    17. Re:Great book, too bad about the software by DocLandolt · · Score: 1

      Well...I'm definitely a 'power user' on Windows -- and as such, I'm just sick of its limitations. Linux is DEFINITELY the answer -- but I happen to be in that awkward position of knowing too much about 'the windows way' and nothing about 'the unix way' ...here are some of my frustrations...

      -- I figured out how to write a bash script, but I haven't figured out how to get it to autorun itself as root on bootup (similar to the 'Startup' folder in windows...I need at least to run a script to fstab my Windows hd)

      -- I figured out how to mount my data drive, but I have to do it through the gui -- I can't figure out the write way to mount a fat drive with fstab in bash (so I can't automount it)

      -- I can't attach my external USB hd (it's one ntfs partition...when I cand find some room to swap its contents, I'll reformat to fat32...that may help)

      -- the buttons on my Vaio laptop don't work right...I've played with all kinds daemons for the sonypi driver, even hacked and recompiled three (a great experiment anyway, and my first good look at ruby, perl and c) but I can't get them to work right (yeah, I know that's Sony's fault for releasing a closed-source driver -- but still agitating when you've gotten so accustomed to using the volume buttons right on the keyboard)

      -- in order to get my speakers to work, apparently I need to have the output at 48,000 hz or something...and apparently I have to do that in alsa..but I don't even know where to begin

      -- shutdown is VERY touchy, and only works occasionally...restart 'always' hangs and hibernate is a freakin' disaster! I've found resources that may help me address this, but it's going to take time...a lot of it, it appears

      Overall, I'm still in love with Linux. I plan on putting a number of people I 'administer' on it -- as soon as I have a good solid understanding of how to tweak it to the point where they won't be able to break it easily, and still do the standard 'average user tasks' much faster and easier than on windows (I'm SICK of cleaning up spyware!)...

      If you're writing a book about how to do THAT, sign me up -- I'll buy your first copy!

    18. Re:Great book, too bad about the software by Anonymous Coward · · Score: 0

      I figured out how to write a bash script, but I haven't figured out how to get it to autorun itself as root on bootup (similar to the 'Startup' folder in windows...I need at least to run a script to fstab my Windows hd)

      Several options (yet another case of TMTOWTDI -- there's more than one way to do it -- in Linux):

      • Add it or call it in /etc/init.d/bootmisc.sh
      • Add and configure a sysvinit script in /etc/init.d using /etc/init.d/skeleton as a template and update-rc.d.
      • Add a cron entry (/etc/crontab or /etc/cron.d) with the '@reboot' special time specification.

      I figured out how to mount my data drive, but I have to do it through the gui -- I can't figure out the write way to mount a fat drive with fstab in bash (so I can't automount it)

      Short answer, in /etc/fstab, add a line:

      /dev/sda /mnt/floppy vfat user,gid=floppy,umask=0007 0 0

      Long answer, see: this LUGOD mailing list post.

      You can also manage this (and other removable / remote filesystems) via automount: aptitude install autofs. See also The AutoFS AutoMounter HOWTO.

      I can't attach my external USB hd (it's one ntfs partition...when I can't find some room to swap its contents, I'll reformat to fat32...that may help)

      Some of the desktops (GNOME, KDE) make this really simple through their file manglers, er, managers.

      NTFS read support should be in stock kernels. Read the NTFS FAQ for details.

      Again, this can be transparently managed under autofs.

      the buttons on my Vaio laptop don't work right...I've played with all kinds daemons for the sonypi driver, even hacked and recompiled three (a great experiment anyway, and my first good look at ruby, perl and c) but I can't get them to work right (yeah, I know that's Sony's fault for releasing a closed-source driver -- but still agitating when you've gotten so accustomed to using the volume buttons right on the keyboard)

      in order to get my speakers to work, apparently I need to have the output at 48,000 hz or something...and apparently I have to do that in alsa..but I don't even know where to begin

      I know both of these are configurable, not my forte. Look for keyboard remapping in Google. Hrm. "vaio laptop keyboard buttons linux" turns up Linux on a Sony VAIO, and suggests 'spicctrl' can do this. A similar Google search may solve your audio problems.

      shutdown is VERY touchy, and only works occasionally...restart 'always' hangs and hibernate is a freakin' disaster! I've found resources that may help me address this, but it's going to take time...a lot of it, it appears

      Frequently disabling ACPI fixes such problems.

      Overall, I'm still in love with Linux. I plan on putting a number of people I 'administer' on it -- as soon as I have a good solid understanding of how to tweak it to the point where they won't be able to break it easily, and still do the standard 'average user tasks' much faster and easier than on windows (I'm SICK of cleaning up spyware!)...

      I hear you on that last. Fortunately Not My Problem[tm] these days.

      Understanding Debian, and in particular Debian Policy, helps immensely in knowing what Debian does and doesn't do, why it does it, and where you (the user/admin) fit in. Policy in general is about carving out which bits are specifically managed by Debian and which are yours to own.

    19. Re:Great book, too bad about the software by chthon · · Score: 1

      Hm, I saved this and sent it to my email address (jurgen.defurne at pandora.be). However, at the moment I am out of internet connectivity because I moved, so it will be probably at least a week before I can look into your questions.

      My goal is to build a database with problems and questions, how to solve them and how to add them to Linux distributions. I find that the biggest problem for people to change over to Linux is that they cannot easily find someone with the right level of expertise, while with Windows they do have that.

      That is the reason that I do not had much problems switching over my dad and my wife, because I am always at their disposal.

  17. 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.

  18. 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?
    2. Re:The Community Sucks by Qzukk · · Score: 1

      Every community is that way, debian's no exception.

      --
      If I have been able to see further than others, it is because I bought a pair of binoculars.
    3. Re:The Community Sucks by Nimey · · Score: 1

      [troll]
      You need to install Gentoo!
      [/troll]

      --
      Hail Eris, full of mischief...

      E pluribus sanguinem
    4. Re:The Community Sucks by Anonymous Coward · · Score: 0
      "...was always the arrogance that just seemed to ooze from the average Debian user. "


      'Cause you know, this sort of generalization is always true, isn't it? Instead of karma I propose instituting pop IQ tests before granting mod points.

  19. BSD on SPARCs - starting to suck, slowly. by Penguinisto · · Score: 1
    "Because installing OpenBSD/SPARC32 on one of those old systems is a complete slam-dunk."

    That I can agree to, on most BSD's (I have 5.2 humming along on an old Netra t1 105 sitting next to my elbow - testing is a breeze on it). --BUT-- That said, FreeBSD 6 on an old Sparc sure is cranky when it smacks right into an old school HME interface...

    Would this mean that BSD support is slipping too? dunno.

    /P

    --
    Quo usque tandem abutere, Nimbus, patientia nostra?
    1. Re:BSD on SPARCs - starting to suck, slowly. by Anonymous Coward · · Score: 0

      I am convinced that Fbsd 6,even release, isn't all thatl. Don't feal bad I have a fairly standard generic PC. FreeBSD 6 --RELEASE has quite a few glitches. For instance the boot.conf lines that were recomended by the handbook and nvidia didn't work at first (copied and pasted) then doing a complete reboot rather than reseting xorg got it working---known bug. Theirs a laundery list of bugs and glitches in it. Some users recomend using just plain vinilla Fbsd 5.4.

  20. Quality control... by ee96090 · · Score: 1, Troll

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

    Now try Ubuntu: good quality control while at the same time keeping up-to-date software in the distribution. Now _that_ is something to brag about!

    --
    Gustavo J.A.M. Carneiro
    1. 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
  21. Re:try Ubuntu Breezy Beaver 5.10 by yosemitesammy · · Score: 1

    Ubuntu Breezy Beaver 5.10

    I switched to it from RHEL4 and FC4 on a Dell Latitude D610 and was *very* pleasantly with the sound/wifi/video/multimedia taht all worked with minimal (ie: NONE) hassles out of the box.

  22. 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 Anonymous Coward · · Score: 0
      contempt for anyone who knows less than them

      less than they...

      /idiot

    2. Re:Debian is for hackers; Ubuntu is for users by Russ+Nelson · · Score: 1

      Sorry; English is my first language.
      -russ

      --
      Don't piss off The Angry Economist
    3. 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
    4. Re:Debian is for hackers; Ubuntu is for users by Anonymous Coward · · Score: 0

      You should be aware, then, that 'less than them' is considered perfectly acceptable by everybody except grammar nazi prescriptivists.

  23. Source by 101percent · · Score: 0, Flamebait

    I actually use Mac OS X and don't use gentoo so please don't say I'm a zealot. But... the only distro that makes sense to use in my mind for GNU/Linux is a source based distro such as gentoo because its all about freedom right, so why would you use a pre-packaged distro? Using gentoo you can practically exercise your freedoms, along with sourcemage and others. Furthermore when using binary packages you can never know what that package does, so unless you compile it yourself you can't be sure. Wait. Actually Ken Thomson or someother wrote about how you can't trust compilers because they can interject code into your binaries. So really you can't trust any programs. Which is why the "GNU is more secure" mantra is patently false. Stop being paranoid Mr. Stallman and just suck it up. Debian could have backdoors too.

    So in the end use Debian if you want a 2 year old system made of binaries that you can't trust, or use a source distro which you also can't trust (at least your exhibiting your freedom in that case). Personally I choose OS X.

    1. Re:Source by John+Nowak · · Score: 1

      It is "you're", not "your", you completely insane man.

    2. Re:Source by Anonymous Coward · · Score: 0

      OS X ... which is of course free and has trustworthy binaries!

      http://funroll-loops.org/

    3. Re:Source by 101percent · · Score: 1

      No binary is trustworthy, and no compiler is trustworthy, so no software is trustworthy therefore.

    4. 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?
    5. Re:Source by 101percent · · Score: 0, Troll

      How is this funny? Its the truth!

  24. Re:try Ubuntu Breezy Beaver 5.10 by mislam · · Score: 1

    What about usb wifi devices? Notably linksys instant wireless 802.11b ones?

  25. Debian Based by BrookHarty · · Score: 1

    There is talk right now how Firefox 1.5 isnt out on Ubuntu because Debian firefox is still at 1.0.7. And debian doesnt know when they will even get 1.5 in testing!

    So, big problem if multiple distro's are waiting on the primary distro for a package with only 2 guys maintaining it, and they have been MIA.

    1. 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
    2. Re:Debian Based by John+Nowak · · Score: 1

      Given the issues with 1.5, I don't see why it would be in "stable" anyway. It is in unstable where it belongs until more of the issues get sorted out.

  26. Old software by Tylerious · · Score: 1

    I used Debian prior to using Slackware (which I use still). Apt-get was what really impressed me. Any package I wanted automatically got its necessary dependancies fulfilled. What disappointed me was the age of the software. For example, I couldn't get XFCE 4.2 on Debian 3.1 simply because the software testing is SO rigorous. Works without any problems on Slackware; don't see what Debian's problem is.

    1. Re:Old software by James+Kilton · · Score: 1

      Aye. Why do people like a package selection that is *at least* one year behind everyone else? I mean is php5 even in testing yet? Apt is a great binary package manager, I'll give it that much, but we have debian at work and I hate having to do any sort of upgrade or finding what package I want to install because everything is so damn old. Now aparently (K)ubuntu's package selection is much more up to date, so I'd go with that if I ever chose a binary distroy. Gentoo and Portage beats it hands down, though.

    2. Re:Old software by Anonymous Coward · · Score: 0

      Everything is so old because the stable release is not meant to change except patch, thus possibly break things. If you really need the newer stuff, you should either run unstable, or stable/testing with some packages from unstable for what you need. They are just level's of guarantee.

    3. Re:Old software by level_headed_midwest · · Score: 1

      Some of the Red Hat variants also offer updates to the latest and greatest software pretty much as soon as it gets out of beta. SuSE has always been that way with updates to KDE and Gnome. I had KDE 3.5.0 literally hours after it was released. Same for 3.4.0 and 3.3.0. And they pretty much always work OK right off.

      --
      Just "gittin-r-done," day after day.
    4. Re:Old software by Anonymous Coward · · Score: 0

      I'd recommend Debian testing for a home desktop system. Here I run Debian testing with GNOME; the version in testing (2.10) is a little old for me, but it's okay as I just build the development release (2.13.5 building now) in /opt/gnome and use that for myself. The rest of the family enjoys a stable, rock solid environment.

  27. 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 Anonymous Coward · · Score: 0

      What about apachectl stop doesn't work for you. Works fine for me on woody and sarge, for apache1 and apache2 (backports.org for woody).

      And have you ever administered many systems of different age and for different purposes? Don't tell me you didn't long for something like FHS-compliance.

      I find Debian changing a bit here and there, but in general they change way less than other distros. Plus, they usually feed their stuff back upstream (like the apache stuff), so it becomes standard.

    2. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      OK, I was using Apache as a hypothetical example. If you want to see what I'm talking about, try installing Qt from source on a Debian system. Notice how the instructions tell you to make the package available at /usr/local/qt.

      Now remove it and install the various Debian packages which make up Qt. Notice how everything is different---binaries are in /usr/bin, libraries are in /usr/share/qt3/lib, headers are in /usr/include/qt3. Try accessing /usr/local/qt/include/qt.h: you can't.

      I've administered systems of different ages and for different purposes, and yes, it is frustrating. But that's because package authors tend to choose poor interfaces, and system integrators then modify these interfaces, making things worse. The FHS is not a solution because it mandates different interfaces for the same package, depending on whether it is ``local'' or part of ``the system.'' I'd love it if all packages used a consistent interface which provided global names that don't change, but that's a decision for package authors, not system integrators.

      Perhaps you are right that some distributions change things more than Debian. But my main point is that Debian mandates these types of changes in their policy.

    3. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 1, Funny

      LOL

    4. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      You can control Apache with apachectl, even in Debian. Indeed, /etc/init.d/apache2 is just a shell script that calls apachectl.

    5. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1

      Sorry, I am indeed mistaken about apachectl. But, as I explained in my other reply, please look at Qt and you will see an example of how different the Debianized package is.

    6. 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
    7. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1

      Sorry, as many have pointed out, I am mistaken about apachectl; indeed, it works fine in Debian. But if you want to see what I mean, look at Qt: 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.

    8. 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.

    9. 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.

    10. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1

      No, the FHS specifically prevents cross-platform compatibility. For example, if a package is installed ``locally'' on one system it will have a different interface than if it installed as part of ``the system'' on another. 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.

    11. 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.

    12. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      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.

      The Debian Apache2 package supports it. It's apache2ctl though.

    13. 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. :)

    14. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1

      Thanks for your comment :) Debian is indeed a superb distro and has some fantastic tools like apt-get. But if we want compatibility across different distributions, we're not going to achieve it by trying to force every package author to fit their package into a specific mold. Linux isn't like that; different parts are maintained by different people who have different styles. We're never going to get everyone to agree on RPM/Deb/FHS/LSB/etc. But if we let the upstream package maintainer decide on the names and locations (i.e. the interface) of his own package, and we stick with it downstream, we might be able to make it work. Note that Debian could add their own FHS-ized interface to a package if they want, they just have to commit to supporting the upstream interface as well.

    15. 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... :)
    16. 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.

    17. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      An alternative is to forsake the shared library cache alltogether, and maintain an ever-growing collection of PATH, LD_LIBRARY_PATH, etc, environmental variables.
      A better alternative is to make your binary depend on the absolute library path of the shared library by passing gcc the -Wl,-rpath flag. This is extremely flexible because the absolute path can be a symlink to whichever version of the library you want your binary to use.

      For instance, let's say I am installing version 1.0 of foo in prefix /package/misc/foo-1.0, and I want it to depend on the default installed version of bar, 0.5. I symlink

      /package/misc/bar -> /package/misc/bar-0.5
      /package/misc/foo-1.0/conf -> /package/misc/bar
      and I tell my binaries in foo-1.0 to always access bar.so by the absolute path
      /package/misc/foo-1.0/conf/bar/lib/bar.so

      (No need to consult /etc/ld.so.conf.) Now, let's say I want to upgrade the default version of bar to 0.6, but I want foo to continue using the older version 0.5 because I know this combination is supported and known to be stable. I can simply change the symlinks to

      /package/misc/foo/conf/bar -> /package/misc/bar-0.5
      /package/misc/bar -> /package/misc/bar-0.6

      No environment variables necessary. And you certainly don't need to ship private copy of libraries with each package.

      Please tell me: How would you accomplish this scenario with an FHS-compliant system (upgrade a dependency for a given set of packages and not others)?

      I know /package can seem strange at first, but once you understand it you'll see that its both simpler and more powerful than the FHS solution. If you're interested look at slashpackage-foreign. This is how I build my systems; I don't even have a file called /etc/ld.so.conf :)

      Oh yeah, I symlink all commands into /command, so I only have one entry in my $PATH :) (Of course, I have /usr/bin, /usr/sbin, /usr/local/bin, and /usr/local/sbin all symlinked to /command for compatibility.)

    18. 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!''

    19. 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.

    20. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      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
      If I write a program which depends on Qt, how exactly is my program supposed to know that? Am I supposed to be aware of where every UNIX-style operating system in the world has decided to put Qt, and then check all these places one by one? Or is each of my users supposed to manually enter the location for Qt, depending on his operating system?
      The symlinks shipped by the Debian packages ensure compatibility with the (IME, inflexible and annoying) layout where everything is in a single directory.
      As I said before, there's relatively little benefit to a package's interface being similar across all platforms (i.e., single directory). The tremendous benefit comes when the interface is exactly the same across all platforms (i.e., I can count on /usr/local/qt/include/qt.h being there).

      And I don't care if you find the layout Qt's authors have chosen annoying. You're free to install Qt wherever you like on your system and then deal with the consequences. But it's ridiculous to subject all Debian users to these hassles, especially since they could be avoided by adding one measly symlink to the Debian package.

    21. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      If I download almost anything as source and compile it myself it will go into /usr/local. That's the entire point of that folder - for locally (non-official) installed packages.

      So either we follow your route, and have everything put into /usr/local, which is fine if it's consistent, or we put it all somewhere else which is consistent. Personally, I like to know that only things I've hand-compiled go in /usr/local, rather than having it a mish-mash of official and local packages.

    22. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      /package/host/openssl.org/openssl/libssl.so
      Sorry, I meant to say /package/host/openssl.org/openssl/lib/libssl.so, but you get the idea :)
    23. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0
      Breaking cross-platform compatibility, as Debian does, for the sake of cross-package similarity is a horrible idea.


      DBJ, welcome back!
    24. Re:Modifying packages to conform to FHS = bad by cortana · · Score: 1
      Any program that requires QT to live in /usr/local/qt3, is *broken* in the first place. The FHS gives us well-defined search paths to locate files:

      If you write your programs to #include <qt/qt.h>, not "/usr/local/qt3", and to have the libqt-mt.so.3 SONAME in DT_NEEDED, rather than (ugh) hard-coding in /usr/local/lib/qt3/lib/libqt.so.3, and so on, then you don't have to know where QT's files actually are. If you are curious, you can always find out with dpkg --listfiles libqt3-mt.

      If the packages dumped all their stuff in /usr/local/$package, you would have to maintain an ever-growing list of directories in which to search for shared libraries, headers, binaries, man pages, etc. Personally I would prefer not to have PATH, LD_LIBRARY_PATH, MANPATH, CFLAGS, LDFLAGS, etc, environmental variables with 10,000 components!

      Something else that you'd lose the ability to do is to share out /usr/share, to make *all* the arch-independant, data in an installation available to machines on a network. This is extremely useful when maintaining a large, heterogeneous network:
      This hierarchy is intended to be shareable among all architecture platforms of a given OS; thus, for example, a site with i386, Alpha, and PPC platforms might maintain a single /usr/share directory that is centrally-mounted.
      -- FHS, chapter 4.
    25. Re:Modifying packages to conform to FHS = bad by cortana · · Score: 1

      I'd rather live with the unmatched convenience of apt, than try to morph my system into some mix of Plan 9 and GNU/Linux.

      At the end of the day, all our software is designed to work with the FHS, and no amount of fraglie automated scripts to create compatability directories for binaries, include files, library files, man pages, info pages, gstreamer elements, pam modules, iptables modules, firmware, bonobo components, gimp plugins, browser plugins, and so on ad infinitum is going to circumvent that.

    26. Re:Modifying packages to conform to FHS = bad by SuiteSisterMary · · Score: 1

      But the entire point of Debian is that 'it's the Debian Way, or the highway.'

      If I wanted things where the installer defaulted them, I'd install slackware and build everything from tarballs.

      --
      Vintage computer games and RPG books available. Email me if you're interested.
    27. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      So either we follow your route, and have everything put into /usr/local, which is fine if it's consistent, or we put it all somewhere else which is consistent. Personally, I like to know that only things I've hand-compiled go in /usr/local, rather than having it a mish-mash of official and local packages.
      It's consistent within your system. The problem is now that my package can't reliably and automatically find its dependencies on all systems. Should it look in /usr, or in /usr/local? If it finds a dependency in both, which one should it use?

      We need to separate the idea of name from the idea of location. Symbolic links let us do just that. You can install packages for your system in different locations depending on whether they are ``local'' or part of ``the system.'' All I'm saying is make sure they are accessible by the default names (using symlinks, if necessary).

    28. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      Mac OS X does this, too. You can't even edit /etc/passwd! And yet people absolutely *love* the Mac. So it apparently isn't "essential".

      What's more, are any sysadmins using Debian going to stop using it because of this? Probably not. Are any Windows or Mac users going to stop considering Debian because of this? Doubtful. Changing this would make *you* happier, but otherwise not have significant effects.

    29. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      What would be even better than symlinks would be some sort of central database that would store information on installed packages. It could tell not only whether a package has been installed, but what version it is, what files it includes and where those files are, what options it was built with, and countless others! I'm going to call it "Package Management", and as soon as I patent it, I'll be rich!

    30. Re:Modifying packages to conform to FHS = bad by roystgnr · · Score: 1

      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.

      Well, by definition it will Just Work for your users, because if people who download your program are running Fedora, Red Hat, Debian, SuSE, Mandrake, or any other distribution that puts Qt where it's supposed to go, then your program won't work at all and they won't become your users!

      I suggest using the QTDIR variable to find your default location, and the linker to find your libraries, and it will Just Work for all users. If you can't figure out how to write correct Qt programs, that's your problem, not Debian's. Demanding that my system become less functional because you don't know better than to use hard-coded pathnames is ridiculous.

    31. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      Any program that requires QT to live in /usr/local/qt3, is *broken* in the first place.
      I don't care if UNIX integrators think it's ``broken.'' The reality is upstream maintainers will choose whichever package layouts they believe are best. You are living in a fantasy world if you think that someday, every package in the universe in going to conform to the FHS. Now given this reality, we are faced with the problem of trying to make interoperability among UNIX-style systems work. The solution is for us all to stop whining and support the standard names with symlinks.
      If you write your programs to #include , not "/usr/local/qt3", and to have the libqt-mt.so.3 SONAME in DT_NEEDED, rather than (ugh) hard-coding in /usr/local/lib/qt3/lib/libqt.so.3, and so on, then you don't have to know where QT's files actually are.
      You're arguing that it's just fine to move files if the files are accessed with the help of search paths: $PATH, $MANPATH, $LD_LIBRARY_PATH, etc. There's no theoretical obstacle to building a complete system along these lines. But it's bad engineering: getting all the details right is a royal pain, and people inevitably screw it up. For example, what happens if you try to upgrade a ``local'' version of slrn by installing a ``system'' package? The program will be put in /usr/bin and the old one will still be in /usr/local/bin. Now users with /usr/local/bin before /usr/bin in their $PATH will invoke the old, undesireable version. Please see FHS failures for more examples.
      If you are curious, you can always find out with dpkg --listfiles libqt3-mt.
      What about on Red Hat? What about on SUSE? What about on the hundreds of other UNIX variants out there? Do you really think its feasible to demand that each package author be aware of where each of his dependencies lives on each different platform?
      If the packages dumped all their stuff in /usr/local/$package, you would have to maintain an ever-growing list of directories in which to search for shared libraries, headers, binaries, man pages, etc.
      No, you don't. I know because I do organize my systems this way. You can use symbolic links to make the files available at their expected locations.
      Something else that you'd lose the ability to do is to share out /usr/share, to make *all* the arch-independant, data in an installation available to machines on a network.
      It is wrong for sharability to determine the name by which a file is accessed. Sharability is not constant. Names must be constant. I can simply set up symlinks like
      /usr/share/qt3 -> /usr/local/lib/qt3/share
      or vice versa to share arch-independent data via /usr/share.
    32. 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

      ?

    33. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1

      /package reuses the filesystem as the database. It provides you with all the package management features you get from traditional package managers, as well as many features they don't provide; for example, adding new files to a package, or declaring that some existing files form a package. A ``central database'' is neither necessary nor desireable.

    34. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      Mac OS X does this, too. You can't even edit /etc/passwd! And yet people absolutely *love* the Mac. So it apparently isn't "essential".
      Cross-platform compatibility isn't essential from the perspective of end users, but it's essential for people who want to efficiently support software on multiple platforms. Haven't you seen how much extra effort goes into ensuring a package works correctly on OS X? I'm not talking about ports which take advantage of the platform-specific features, like Carbon Emacs. I'm talking about getting a package working on Mac that generally works fine on other UNIX variants. Chances are you won't be able to compile it out-of-the-box. Overall, countless hours are wasted just because Apple decided to rename GL/gl.h to OpenGL/gl.h and not support the standard interface. Mac users are actually suffering indirectly from the dilution of support resources, even if they don't realize it.
      What's more, are any sysadmins using Debian going to stop using it because of this? Probably not. Are any Windows or Mac users going to stop considering Debian because of this? Doubtful. Changing this would make *you* happier, but otherwise not have significant effects.
      Wrong. Do you realize how much extra effort is required by maintainers and third-party software vendors to support their packages on dozens of different UNIX variants? That's because most of the variants apply tweaks that make their package interfaces incompatible with other platforms. In short, they're throwing away the efficiencies of the mass markets. We'd all have better software if UNIX integrators cared about cross-platform compatibility.
    35. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      I'd rather live with the unmatched convenience of apt, than try to morph my system into some mix of Plan 9 and GNU/Linux.
      apt is indeed a nice interface to package management; however, nothing about it is inherently tied to the FHS. It could be made to work with other package layouts.
      At the end of the day, all our software is designed to work with the FHS, and no amount of fraglie automated scripts to create compatability directories for binaries, include files, library files, man pages, info pages, gstreamer elements, pam modules, iptables modules, firmware, bonobo components, gimp plugins, browser plugins, and so on ad infinitum is going to circumvent that.
      You'd be surprised how at how much less work it is than you think. sp-foreign is 5268 lines of Bourne shell scripting on my system. Compare this with dpkg and all the Debian packaing infrastructure. Granted, they have different requirements and different goals, but my point is that an non-FHS system is do-able.
    36. Re:Modifying packages to conform to FHS = bad by grosskur · · Score: 1
      I suggest using the QTDIR variable to find your default location, and the linker to find your libraries
      We could use search paths for everything, but getting the details right is a royal pain and people inevitably screw it up.
      Demanding that my system become less functional because you don't know better than to use hard-coded pathnames is ridiculous.
      Do you realize how silly this sounds? Your system is functional precisely because it uses tons of hard-coded pathnames. Ever tried changing the location of /bin/sh? How about /dev/null? What about /etc/fstab?
    37. Re:Modifying packages to conform to FHS = bad by Anonymous Coward · · Score: 0

      Cross-platform compatibility isn't essential from the perspective of end users, but...

      If it's not essential to my users, it's not essential. Really.

      Haven't you seen how much extra effort goes into ensuring a package works correctly on OS X?

      Exactly: it's such a great system for so many people -- they love it *so* much -- that maintainers do anything to get software working there.

      This has long been an advantage of Macs. Their users can be so fanatical, it's hard to imagine what would kill the Mac. Apple has weathered things that would have killed any other company.

      I'd rather have Linux in that position -- users so passionate that developers would go the extra mile for them -- than try to sell something to my boss (hypothetically -- my boss digs Unix) that's vague and abstract like "if you make it cross-platform, it's more efficient for maintainers". Eh.

      Overall, countless hours are wasted just because Apple decided to rename GL/gl.h to OpenGL/gl.h and not support the standard interface.

      Maybe. Maybe budding Mac hackers poking around their system recognized "OpenGL means 3d graphics", and found it easier to get started, rather than seeing a random combination of letters. If you're porting software to the Mac, the location of gl.h is the least of your concerns -- and you probably already know how to deal with it. Personally, I try to always do the best thing, not simply what everybody else is doing; calling OpenGL "GL" for no good reason (too many letters to type?) is something I can live without.

      We'd all have better software if UNIX integrators cared about cross-platform compatibility.

      It sounds like you're saying we'd have *more* software, not better software. I think if we gave things longer and clearer names, that would be "better".

      My Linux system has gobs of crappy software. I don't need more software; what we need is better software, and not in the sense of "same include files as BSD", but in the sense of "user interface isn't craptastic".

      What I'm trying to say is: If we have a system that people adore, it won't matter all that much if our include files aren't exactly the same as NetBSD's. But if we have a system that people hate (or, just as bad, are indifferent to), compatibility won't matter a bit.

      Cross-platform source code is nice, in the same way that having nicely-formatted source code is nice. Once it's in the user's hands, it doesn't matter.

  28. The best, maybe, but installation? by SparksMcGee · · Score: 1
    Disclaimer: This is a very thinly veiled request for tech support


    I've had Ubuntu installed for ages--installation went smooth as butter--on a second 250GB hard drive with 200G of NTFS scratch space (for use by my first hard drive's Windows installation). I've heard some very good things about Debian and, as I've had a few issues with Ubuntu (can't seem to install the video drivers correctly, though I've heard this is a problem specifically with the Hoary release--stuck at a blurry non-native resolution--largely I just want something somewhat more bare bones), I've spent some time trying to overwrite the existing Linux installation with Sarge Debian, only to find that it just. will. not. do. it. The installer can't mount the second hard drive. period. It'll mount the first and primary (NTFS-formatted, Windows booting) hard drive just fine and offer to overwrite the whole shebang, but even disconnecting that hard drive and connecting the second as the only and primary device, it can't mount the thing. Googling, reading TFM, etc. all seem to provide some promising leads as far boot paramters, etc.,but nothing seems to pan out. My working theory is that the 2.4 kernel just can't mount a drive of that size (there seems to be evidence to support this on older versions of 2.4, 2.4.12 and earlier, I belive, though I imagine that Sarge would be using the latest available release), and that this explains the disparity between the 2.6-based Ubuntu installation and the 2.4 Debian non-installation. Although I'd really like to give this "dream OS" a shot, I'm very tempted to skip it and just go with Gentoo, especially since it's alleged to have a very good build for AMD64. Insight from the /. community?

    1. 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...
    2. Re:The best, maybe, but installation? by poopdeville · · Score: 1

      Try Debian with a 2.6 series kernel? Sarge can use either. Testing and Unstable install 2.6 by default (though, iirc, so does Sarge)

      --
      After all, I am strangely colored.
    3. Re:The best, maybe, but installation? by Anonymous Coward · · Score: 0

      Depending on your needs, try out FreeBSD too (maybe OpenBSD and NetBSD too).

    4. 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.
    5. Re:The best, maybe, but installation? by paulkoan · · Score: 1


      I have found that Ubuntu is more sensitive to hard drive Master/Slave/CS jumper positions than say Windows.

      I had no jumper on a WD drive, and it just wouldn't take it until I jumpered it as master.

      Windows didn't bat an eyelid.

      --
      This signature intentionally left blank
    6. Re:The best, maybe, but installation? by BiggerBadderBen · · Score: 1

      As others have mentioned, you can install a 2.6 kernel with Sarge. The current stable version is 2.6.8, although I read somewhere that 2.6.11 will soon be validated.

      To do this, insert a Debian 3.1 boot CD and type 'linux26' at the boot prompt. Once everything's installed you can point to unstable and get even newer stuff if you like living on the edge...

    7. Re:The best, maybe, but installation? by thegoldenear · · Score: 1

      linux26

    8. Re:The best, maybe, but installation? by thegoldenear · · Score: 1

      If you know your problem is fixed with 2.6 then use 2.6 from the installer: instead of pressing 'Enter' or 'typing 'linux' at the installation prompt, type 'linux26'.

    9. Re:The best, maybe, but installation? by arivanov · · Score: 1

      So what exactly is your problem?

      Debian ships with both 2.4 and 2.6, just use the 2.6.

      Enter linux26 on the initial boot prompt and off you go.

      As far as 2.4 is concerned it should read drives above 137GB, but it may have problems with some hard disc controllers. If you are running new or esoteric hardware 2.6 is definitely your answer.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    10. Re:The best, maybe, but installation? by ObsessiveMathsFreak · · Score: 1

      Try Debian with a 2.6 series kernel? Sarge can use either. Testing and Unstable install 2.6 by default (though, iirc, so does Sarge)

      However, if you really want a 2.6 kernel, you should probably go with a distro whos stable branch supports it.

      --
      May the Maths Be with you!
    11. Re:The best, maybe, but installation? by poopdeville · · Score: 1

      Sarge is the stable branch.

      --
      After all, I am strangely colored.
    12. Re:The best, maybe, but installation? by Anonymous Coward · · Score: 0

      However, if you really want a 2.6 kernel, you should probably go with a distro whos stable branch supports it.

      Like Debian, in fact. Uh... what was your point again?

    13. Re:The best, maybe, but installation? by poopdeville · · Score: 1

      Word. I looked up my installation disc, and 2.6 is installed by default in the PPC version. Must be different on other platforms.

      --
      After all, I am strangely colored.
  29. You MUST Be Kidding by c_spencer100 · · Score: 1

    good quality control while at the same time keeping up-to-date software in the distribution

    Here's a perfect that totally disproves that statement:

    I used Ubuntu 5.10 for a few months. The problem with Breezy Badger is the version of Firefox that ships with it is just awful. Aside from the terrible memory leak, it randomly segfaults on different links. Here's the problem: Ubuntu won't backport 1.5 to Breezy Badger. Why? Because that repository that they're always bragging on kicks you in the teeth. All those plugin packages are broken by the upgrade to Firefox 1.5. In fact, since the upgrade breaks so many packages (somewhere in the neighborhood of 50), Firefox 1.5 won't be backported. All this just to upgrade a simple browser. Don't waste your time reporting the bug to Firefox, because they'll quickly close your thread and tell you that it's fixed in trunk. Of course you could easily install it yourself, but isn't package upgrade and availbilty one of Ubuntu's biggest selling points?

    ps. Is that how CmdrTaco wanted us to link to stories ;)

    1. Re:You MUST Be Kidding by Anonymous Coward · · Score: 0

      If you think firefox is a "simple browser" you clearly have not read the link you posted. Firefox is the HTML rendering library for a lot of software in Ubuntu! And unfortunately it's not API or ABI stable.

      Ubuntu uses firefox to build packages that use Gecko, while Debian uses mozilla. Other than that, your rant applies to both.

      If the Ubuntu people actually wanted to backport firefox they could just create a new package called firefox1.5, or rebuild and test all packages that depend on firefox (which is not something you want for a stable distro).

      Anyway, it seems you should be ranting at firefox for not making a stable enough release that you need so bad to upgrade, and for not keeping API and ABI stability. This causes a problem for Ubuntu users that can be easilly fixed, if you (again) just read the link you posted.

    2. Re:You MUST Be Kidding by ee96090 · · Score: 1

      > The problem with Breezy Badger is the version of Firefox that ships with it is just awful.

      That's not Ubuntu's problem. That was the best firefox version that was available at the time Breezy was released. Dapper (next release, currently unstbale) already has firefox 1.5.

      --
      Gustavo J.A.M. Carneiro
  30. Agree by Britz · · Score: 1

    I completely agree with Krafft on everything he says in the interview (at least the stuff I understand). I am not a developer nor great coder. I am only a Debian user, but my first install was Slink and I have been seriously into Debian since Potato.

    Don't get me wrong, I hate Debian, but only because it is the only OS installed on my machines. I couldn't live with the rest, because they are far worse than Debian. IMHO Sarge went a little downhill, there were some rough edges during release. For example the security team in reality only existed of Joey (met that guy a couple month ago, he is smaller in real live), but that was just one of the obvious things. If you do a lot of administration for both Potato and Sarge (yes Potato still runs happily on many machines, not only on mine) you know what I mean.

    I didn't know there was so much trouble with Ubuntu/Canonical, but as Debian and/or Ubuntu developers they ought to know better. For some reason many people want/ed to make Debian more "desktop/user friendly" (shudder), whatever they mean by it. I think the idea and philosophy of Debian is perfect for what it is and I really hope the people that were in Debian and thought so left for Ubuntu. Ubuntu is great in itself.

    RTFM!!! it is great

  31. laptop/wifi by handbooker · · Score: 0

    after experimenting with several distros on my laptop, mepis (debian-based) has been the only one to get my wifi working straight out of the box.

    and with mepis, you get the lovely advantage of using debian package management (which means near-amazing software access) without having to download 14 iso's. actually, using mepis has made me a debian fan.

    but when will debian put out their own self-contained one or two disc version? i think that alone would win users to the cause, and maybe silence some who might say debian is just a "good base" to spin other distros off of.

    1. Re:laptop/wifi by John+Nowak · · Score: 1

      You only need the first disc. They even offer a business-card sized disc which grabs what it needs from the net. I don't know anyone who uses all twelve discs.

  32. Gentoo by bipolarpinguino · · Score: 1

    I do believe one can trust an open source program. If you don't like what's going on, why don't you take a peak into the source... That being said, Gentoo is my distro of choice. Apt is nothing compared to Portage. If you have the 3 days it takes to install, it's definately worth it to spend that time setting up a nice gentoo system. Debian is nice, but I really only need it when I need to get a server up and running in under two hours. I recommend it to new linux converts since the set up is highly automatic and it's really easy to use.

    1. Re:Gentoo by Anonymous Coward · · Score: 0

      If all you need is a "server up and running" then a stage 3 gentoo installation without X can take less than an hour with apache, vsftpd, and other services. Maybe two if you want more complex things or the LiveCD is a few months old and you want updates. The only thing about installing gentoo that takes significant time is installing GUI's. And, except for KDE, all the large, slow-compiling C++ apps have binaries mostly.

    2. Re:Gentoo by Anonymous Coward · · Score: 0

      Heh, how is portage better? After installing common packages, they are frequently not set up or even close to being usable. Apt(aptitude) goes through and asks you for settings. I can't pick out a config setting message as the text flies by in a compile. I can however just download a binary that's probably works pretty well and have the installer configure it for me.

    3. Re:Gentoo by bipolarpinguino · · Score: 1

      Forgot to mention, Gentoo also has binaries available for install through portage as well as the source, so what now, Apt?

    4. Re:Gentoo by bipolarpinguino · · Score: 1

      Debian has a much nicer set up and configuration.

    5. Re:Gentoo by Wyzard · · Score: 1
      Forgot to mention, Gentoo also has binaries available for install through portage as well as the source, so what now, Apt?

      As Krafft said in the interview, Apt is just the tip of the iceberg -- you can't characterize a whole distribution by its package manager alone. That goes for Gentoo as well: Portage is nice, but it's not the one and only thing that differentiates Gentoo from the rest. Both are great distributions, and my "ideal" would be a hybrid of the two, but you really can't just say "Apt is nothing compared to Portage", without even any supporting argument, and conclude from this that Gentoo is superior to Debian. Logic doesn't work that way.

      And people say Debian users act too high-and-mighty about their distribution...

      (As I write this, BTW, I'm in the process of installing Gentoo in VMware on a Debian host.)

  33. 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
  34. Re:try Ubuntu Breezy Beaver 5.10 by Anonymous Coward · · Score: 0

    ndiswrapper? Although breezy does ship with an ancient version and I had serious difficulties getting anything more recent to compile even after installing gcc 3.4. Dapper comes with 1.5 at the mo, but it's obviously a moving target and not recommended for serious use yet.

  35. Re:try Ubuntu Breezy Beaver 5.10 by yosemitesammy · · Score: 1

    I don't know... mine was a Intel mini-PCI card using the ipw2200 driver..

  36. PITA Printing in Debian by bdwoolman · · Score: 1, Insightful

    Thank God somebody else finds this to be the case. So I'm not a complete idiot after all. (or at least not the only complete idiot.) Thank you. I got my printer to work but only in some kind of half arsed crippled kind of way. It is an HP and supposed to be fully supported. Feh!

    --
    "No fear. No envy. No meanness." Liam Clancy
    1. Re:PITA Printing in Debian by daliman · · Score: 1

      I didn't think it was any harder than any other Linux printer setup; I just wanted to know how it was done, as the original poster seemed to think it was easy.

  37. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  38. No problems here by Anonymous Coward · · Score: 0

    Debian was actually the only Linux I could get to work on my Blade 100. I had to do the netboot install but it worked almost as easy as an Ubuntu install. Works great.

  39. Linux archeology by Anonymous Coward · · Score: 1, Funny

    "What was Linux like in the early 1990's Daddy?"

    "Install Debian stable son, see for yourself."

    1. Re:Linux archeology by Anonymous Coward · · Score: 0

      Then, once the kid wants to move on to the mid-90's....

      "Slackware Linux, the very best 1995 has to offer."

      Sorry, I just love those Linux demotivational posters

  40. 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
  41. bwhahahahah! by Anonymous Coward · · Score: 0

    I love my macs and your comment is so true...

  42. UHG by violent.ed · · Score: 0, Troll

    This is a difficult question. I learnt a lot of technical stuff about the Debian system, but I cannot identify "the most important thing," so I'll have to look elsewhere: the community. I definitely learnt that my initial plans to "write a book about Debian" wouldn't have worked without the countless folks who helped out.

    OMFG! I don't know if I should smash the article's author's head in with a shovel or the actual author of the book for using the "word" learnt!!! It is LEARNED, as in I LEARN in school, and I use what I LEARNED in my current career choice.

    flame me for spelling or grammar typos, i dont care, this is just my own rant against whoever it is who allowed the word "learnt" into such a decent article! ... btw, doesn't learn/learned look weird? Shouldn't it be Lurn/Lurned?

    --
    - You're not paranoid, they really are after you.
    1. Re:UHG by teebob21 · · Score: 1

      Well, you provided the flamebait, but I won't provide you the satisfaction. Learnt, verb, past tense. From: http://dictionary.reference.com/search?q=learnt v. learned, also learnt (lûrnt) learning, learns v. tr. 1. To gain knowledge, comprehension, or mastery of through experience or study. Also, I spell it "Ugh". 2. To fix in the mind or memory; memorize: learned the speech in a few hours. 3. 1. To acquire experience of or an ability or a skill in: learn tolerance; learned how to whistle. 2. To become aware: learned that it was best not to argue. 4. To become informed of; find out. See Synonyms at discover. 5. Nonstandard. To cause to acquire knowledge; teach. 6. Obsolete. To give information to.

      --
      khasim (12/9/06): In a blind taste test, more people preferred Coke over the Pepsi that I had previously pissed in.
    2. Re:UHG by Anonymous Coward · · Score: 0

      Not everyone is American.

      From Merriam-Webster Online: "chiefly British past and past participle of LEARN"

    3. Re:UHG by violent.ed · · Score: 1

      Touché. i shall now hang my head in shame.

      --
      - You're not paranoid, they really are after you.
  43. 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.

    1. Re:Debian Annoyances by LodCrappo · · Score: 1
      /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.

      update-rc.d ?

      --
      -Lod
    2. Re:Debian Annoyances by Schraegstrichpunkt · · Score: 1
      I mostly agree (and I still use Debian) but...

      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.

      It happens to me, on occasion. I usually edit the script in /var/lib/dpkg/info/, find the offending rm or rmdir line (which is usually the problem), and append || true to it.

      I should probably start filing bug reports with patches for these packages one of these days...

    3. Re:Debian Annoyances by An+Audience+of+One · · Score: 1
      /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.

      update-rc.d

      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.

      This isn't true, all these packages use the dpkg package list, and install packages with dpkg. The package list will always be in sync between them. Some of the fringe things *are* different (dpkg --set-selections holding, for example), but I consider this a bug.

    4. Re:Debian Annoyances by Jussi+K.+Kojootti · · Score: 1
      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.
      I have no idea what front-ends you used, but my experiences with apt-get, aptitude, synaptic and straight dpkg have been very positive. No package inconsistencies.
    5. Re:Debian Annoyances by cortana · · Score: 1
      /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.
      If removing the relevant links from /etc/rc[0-6].d is too difficult, you can use sysv-rc-conf, sysvconfig, or any of your other favourite tools in Apt. GNOME and KDE also provide interfaces to enable/disable services; GNOME's is located under Desktop -> Administration -> Services.

      It's true that policy doesn't mandate the existance of a 'status' argument for init scripts; however, it does mandate that init scripts are idempotent, and in the few cases where I have genuinely wanted to check if a daemon is running rather than start/stop/restart/reload it, I just use the tools in procps.
      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.
      AFAIK, adduser is not supposed to. There can be no general frontend for modifying the data behind NSS, because it can be stored in so many different ways. If there are scripts in another distribution you would like to see packaged, please run 'reportbug wnpp' and fill in a Request For Package bug.
      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.
      This has nothing to do with ideology. The OpenSSL license is not compatible with the GPL, because it imposes additional restrictions on the use/modification of the GPLd code. It is simply illegal for Debian to distribute GPLd binaries linked to OpenSSL; anyone else who does so is opening themselves up to lawsuits. See the archives of debian-legal or OpenSSL and the GPL for further information.
      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.
      I can't say I understand what you mean. I use both apt-get and aptitude, and there are no issues with data consisitancy.
      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.
      True, however the failure of such scripts is a critical bug, and will result in a package being kicked out of the release if not fixed. Anyway, when the need arises, it's hardly 'nearly impossible' to edit the offending {pre,post}rm script and (at worst) comment out the failing command. ;)
    6. Re:Debian Annoyances by ichin4 · · Score: 1

      Well, I certainly appreciate the time you and other have taken to address my annoyances list.

      On a few points, I stand corrected. update-rc.d certainly does init script management, although as you say nothing produces a nice formated overview like RedHat's tools. And I mis-stated my problem with different package management front ends. I know I did have a problem -- perhaps apttitude didn't recognize a package installed with dpkg --set-selections, or didn't respect a pinning I had done with another tool -- I don't remember exactly how I got burnt, but I certainly didn't accurately descibe the issue in my post.

      On OpenSSL and GPL, I think you are being a bit disinginuous. Many other distros with a lot more high-paid legal talent than Debian have concluded that the OS clause gives them a usable legal loophole. But instead of seeking to use the loophole to benefit its users, Debian sought ideological confrontation. Debian's attitude toward the binary-only nv drivers is another example. I spent a couple hours installing the binary driver and getting GL working just so my daughter could play penguin racer. Other distros would install it by default.

      I don't know whether others distros have an adduser that functions as a shim for multiple NSS data stores, but I know I'm not the first "enterprise" admin to suggest it. The excuse that "it's not supposed to work that way" is a little weak. The sendmail command wasn't orginally supposed to be a shim over whatever email system you used, but Debian and other distros now make it one, because it's damn useful to do so.

      Anyway, thanks again to all of you for responding.

    7. Re:Debian Annoyances by JonJ · · Score: 1

      Debian's attitude toward the binary-only nv drivers is another example. I spent a couple hours installing the binary driver and getting GL working just so my daughter could play penguin racer. Other distros would install it by default.
      That's not many. Fedora Core doesn't, and I found it alot easier to install the nvidia-driver with apt and module-assistant, then on Fedora Core systems. SUSE does not ship with it(Available through YOU, I know), Slackware doesn't, Ubuntu doesn't. Some do, that's true, but most doesn't.

      --
      -- Linux user #369862
  44. Countering Trusting Trust through Diverse Double-C by pkhuong · · Score: 1

    You can test the compiler's trustworthiness.

    http://www.acsa-admin.org/2005/abstracts/47.html

    Countering Trusting Trust through Diverse Double-Compiling

    David A. Wheeler
    Institute for Defense Analyses
    USA

    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. If this attack goes undetected, even complete analysis of a system's source code will not find the malicious code that is running, and methods for detecting this particular attack are not widely known. This paper describes a practical technique, termed diverse double-compiling (DDC), that detects this attack and some unintended compiler defects as well. Simply recompile the purported source code twice: once with a second (trusted) compiler, and again using the result of the first compilation. If the result is bit-for-bit identical with the untrusted binary, then the source code accurately represents the binary. This technique has been mentioned informally, but its issues and ramifications have not been identified or discussed in a peer-reviewed work, nor has a public demonstration been made. This paper describes the technique, justifies it, describes how to overcome practical challenges, and demonstrates it.

    --
    Try Corewar @ www.koth.org - rec.games.corewar
  45. 3.1. Re:All I know is... by freedom_india · · Score: 1

    I can't seem to find 3.1 version's graphics's installer anywhere !

    It says "Removed because..."

    Any idea where else i can find the 3.1 graphical installer (even if only beta/alpha?)

    --
    "Doing what i can, with what i have." ~ Burt Gummer
    1. Re:3.1. Re:All I know is... by wild_berry · · Score: 1

      I don't think Sarge (Debian 3.1) has a graphical installer. Sarge's Installer page lists downloads which use the NCurses-based text installer. I think you can get the graphical installer with the present 'testing' distribution, Etch, which is expected to become the 'stable' Debian release in December, at this page.

  46. good book... but only for most serious debian user by jackstack · · Score: 1
    I've read through substantial portions of the book and think it's very good. HOWEVER - keep in mind that the book is definitely not meant to show you how to use linux and barely even to show you how to use debian for mundane tasks.

    It largely shows you what is behind debian and how it is made up. It really gives you a sneak peak of what the inner-core of the debian community is like. I liked the one chapter that shows a map of how a program gets turned into a debian package. It shows what steps are done manually and what is done automatically with scripts. The book also goes into detail on debian-specific user an developer tools.

    My lasting impression is that the book reveals how a tight developer and package maintainer community is really what delivers such a great product. If you have no interest in this topic, this book is not for you.

  47. debian.packages.org hit by /. !! by Mr+Europe · · Score: 1

    This is what I got from packages.debian.org

    "packages.debian.org is down at the moment due to performance issues.
    We apologize for any inconvenience and hope to have service restored as soon as possible."


    It looks like every /. reader is installing Debian !

  48. Re:debian.packages.org hit by /. !! by heanol · · Score: 1

    It's been like that for weeks..

  49. guides to setting up Debian at thegoldenear.org by thegoldenear · · Score: 1

    I have guides to setting up Debian desktop systems that describe which packages to choose for various desktop tasks and how to configure them, for Debian 3.1 Sarge and for Debian Testing.

    And a similar guide for a Debian server.

  50. 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!
  51. The Debian System Explained by Anonymous Coward · · Score: 0

    The Debian System Explained:

    Utter shit.

  52. OT: What is a ``, anyway? by Anonymous Coward · · Score: 0

    They're backticks, not opening quotes. Why do UNIX nerds insist on playing at typographers like ``this''?

    It looks CRAP. This is not an xterm.

    Use a double quote mark ".

    1. Re:OT: What is a ``, anyway? by grosskur · · Score: 1
      backtick, conveniently enough, can serve as an open quote. It looks different from apostrophe, which can serve as a closing quote. This has the effect of making each type of quote distinct (i.e. you can easily tell where a quote begins and ends), whereas with typewriter quotes, the opening and closing quotes look exactly the same.

      Get a better font (i.e. one with slightly curvy quotes) and it will look better to you.

    2. Re:OT: What is a ``, anyway? by Anonymous Coward · · Score: 0
      No. Wrong.

      This: ` is a backtick. It is neither an apostrophe: ' nor an opening single quote: ‘.

      If you're really going to be typographically correct, you should use LDQUO and RDQUO entities “like this” or LSQUO and RSQUO entities ‘like this’.

      It doesn't look "distinct", it looks like a UNIX nerd never realised that the world stopped being an xterm in about 1996.

      If you're displaying HTML, use entities. If you're displaying plain text, use typewriter quotes. Anything else is typographical bollocks.

      Some reading for you, that you may become enlightened:

      http://www.cs.sfu.ca/~ggbaker/reference/characters /

      http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ ruby-talk/3010

    3. Re:OT: What is a ``, anyway? by grosskur · · Score: 1
      It doesn't look "distinct", it looks like a UNIX nerd never realised that the world stopped being an xterm in about 1996.
      LOL :)
      Some reading for you, that you may become enlightened
      Thanks for the links; I hadn't seen the subject discussed at length before. I'm going to look into it some more and possibly reconsider my (ab)use of the backtick :)

      Ideally, I'd like to just use Unicode characters directly (not entities) for open and closed quotes, but I can't do this until I'm confident all clients are using Unicode (lots of people still use various legacy character sets ATM).

  53. Re:Assembly by pedestrian+crossing · · Score: 1

    Do it in assembly language- that would certainly be unique.

    But not very portable #:-(

    --
    A house divided against itself cannot stand.
  54. Debian system... didn't that have 2 suns? by Anonymous Coward · · Score: 0

    I am obviously the wrong sort of geek to enjoy this. All I could think of was Star Trek...

  55. /etc/init.d/httpd was maliciously deleted! by Anonymous Coward · · Score: 0

    Not, apachectl. I will never understand the hatred the Debian guys have for the standard way of doing things. What do they gain from trying to force the rest of the world to call httpd by the name apache. It's breaks a lot of scripts, and it's very hard to remember when you're on a normal system versus a Debian proprietary system so you know what to type.

  56. if you want "bare bones" why use Ubuntu? by walterbyrd · · Score: 1

    Why not just go with stright-up debian?

    If you have broadband, I would recomend the 100mb download. Upgrade the kernel, and change to testing or unstable, if you like. Then if you want a gui, do an apt-get x-window-system, and an apt-get icewm (or whatever) and you're in business. Have the system set up just for what you want, and no cruft.

    It is a bit of work, but it's educational. And once you have you installation, you may never need to re-install, just keep upgrading.

  57. Re:good book... but only for most serious debian u by Anonymous Coward · · Score: 0

    check out this site http://debian.home.pipeline.com/ for an updated Debian packaging diagram (soon to be in pt_BR). -Kev

  58. Re:Countering Trusting Trust through Diverse Doubl by pkhuong · · Score: 1

    You don't know your history.

    "Reflections on Trusting Trust
    Ken Thompson
    Reprinted from Communication of the ACM, Vol. 27, No. 8, August 1984, pp. 761-763."

    http://www.acm.org/classics/sep95/

    "Again, in the C compiler, Figure 5 represents the high-level control of the C compiler where the routine "compile" is called to compile the next line of source. Figure 6 shows a simple modification to the compiler that will deliberately miscompile source whenever a particular pattern is matched. If this were not deliberate, it would be called a compiler "bug." Since it is deliberate, it should be called a "Trojan horse." "

    Yes, this is the exact paper Wheeler (and probably the great grandparent, implicitly) refers to. Yes, it was in 1984. Yes it was practical enough back then that it was actually done. Yes, it would still be practical today.

    Note that this is not what Wheeler's paper is about. Wheeler's paper is about knowing when such a trojan has been implanted in the binary compiler (which then propagates it whenever it compiles itself).

    --
    Try Corewar @ www.koth.org - rec.games.corewar
  59. I don't get this. by hummassa · · Score: 1

    I used to use Debian Sid, but I am a Kubuntu converted. For the last three years, when I want to setup a printer, I go to the "System Configuration" app (was "control panel" or something before, but...), click on the "printers" icon (under the "hardware" title), see the now-installed printers, click on "add new printer", fill out the needed info (it even searches for printers in a Windows network for me), print a test page and voila. In the same applet, I can pause or delete a job, configure printer parameters, etc... what is so difficult?

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  60. Some hardware configs are smoother by bdwoolman · · Score: 1

    The automatic stuff in system config did not work properly. Ultimately I was able to get a driver loaded and print. I have an older MB on my machine and parralel printing. Anyway, it is no big deal. Just a bit of a hair puller. Glad your experience was more standard. Most have no problems. Just downloaded the Kubuntu iso as it turns out. Will overwrite current system. Trying to find a distro that likes my setup. If it works better I'll repost. Could be a while. Cheers, B

    --
    "No fear. No envy. No meanness." Liam Clancy