Debian has a very stable bare bones server setup. It's once you begin to install most of the GUI apps, a person is bound to run into trouble. For some odd reason Debian tends to believe they can write better code than upstream, and their ideas must be imposed upon the user. Occasionally (not always
) these patches have been known to cause a few stability issues, notably with multimedia packages.
Another issue with these Debianified packages, is that if there is an upstream bug with a trivial upstream patch released to fix the issue - it is not
a simple method to build, patch, and package an official Debian package. You're at the whim of one of the 10,000's Debian packagers. Then you need to hope this fix gets back ported, or try your luck running mixed repos and play with apt-pinning, worry about the dependency tracker stating somelib1.2.2-debian3 is different than somelib1.2.2-debian2 even though the source is exactly the same, and the Debian diff only reads +somelib1.2.2-debian3 -somelib1.2.2-debian2, which causes apt to tell you to update 550 packages only to get the bug fix for mousepad's find function
There's another issue with Debian stable. Once Debian Stable
is released, a great deal of the software is outdated, and will become antiquated (in software terms) before the next Stable
Slackware also has an extremely stable bare bones server setup. Due to Pat and the team's critical evaluation and testing of other packages - only those which they choose make it through to current, then onto stable. Slackware's nature is to patch only if absolutely necessary. This greatly limits the ratio of packager caused bugs, and adds the ability to directly track upstream. Should a released package have an upstream bug, in which upstream does release a patch for, it's extremely simple to add the patch command to the SlackBuild, and build an official proper Slackware package. Slackware also has the pleasure of some what new and current packages, with a release just about twice a year.
So, on the onset, both Slackware and Debian are each extremely stable. It's the maintainer-ship, longevity, and ability to self administer in which Slackware whoops up on Debian
System stability is more than getting a login prompt 2 minutes after installation.