Slashdot Mirror
Introduction to Debian
[vmlinuz] writes "SitePoint has an article that I wrote that introduces Debian and has guidelines on installing it. This could be usefull for managers, new users and other people that may be interested in using Debian." And honestly, who among us isn't interested in using the obviously superior Linux Distribution against which there can be no other contenders? (Oh dear god don't flame me! It's a joke people!)
I'd like to be able to pin the newest KDE/gnome/whatever to stable and do an apt-get upgrade without breaking a million things.
You can pin the newest KDE/gnome/whatever to unstable. Newest always goes in unstable first. Unstable is pretty cutting edge, but with an occasional hiccup.
The point of stable is that it works. Things go there after they are 'tried and true' in unstable, and then in testing.
Hey, don't forget Knoppix.
But, for those of you who want the bleeding edge without risking instability, Debian does just fine there if you know what you're doing. Go ahead and jump to unstable. Seriously!
The only thing you're missing is "apt-listbugs," which does this automatically with every update...
Before starting installation, apt-listbugs fetches all the bug reports for versions between your current version and the target version. We can see that two bugs have been closed (fixed by later versions, or the bug reports were bogus), and we see that the tetex-bin bug is still open.
In this case, we'd type 'h tetex-bin' to hold the broken package and proceed with a perfectly usable system.
Of course, this still leaves you in the position to be the one in ten thousand who finds a critical bug on installing any given package. If that happens, be a Good Debizen and use reportbug so the next guy is notified. Further, if you flag a critical bug, it's rare that it isn't fixed within a couple hours, even at 2am on Sunday. Once you've reported your bug, go ahead and roll back a version and carry on until the developer closes the bug -- if you used reportbug, you'll get an all-clear email automatically when he or she closes the bug.
With unstable and the apt-listbugs' automatic reports, the chances of ever winding up with a broken system are exceptionally low. Showstopper bugs are rare even in unstable -- maybe one package update in five thousand. But, with thousands of other users snarfing packages and reporting any bugs, the chances of your being the one to discover breakage without apt-listbugs warning you first are virtually nil.
All that said, if you can bear to be a week to a month behind the bleeding edge, you can use apt-listbugs with testing as well. The chances of getting a broken system with testing and apt-listbugs are about the same as the chance of Windows Service Update not needing a reboot. Virtually nil.