Adam Funk wrote:
So are there any practical disadvantages to running unstable instead of testing?
A couple of years ago a bug found its way into PAM in unstable, and caused a lot of unstable users to be unable to log into their machines. testing users, IIRC, did not get that problem, as it was resolved before the package trickled into testing.
Currently, unstable on a Sun Blade 2000 (Sparc architecture) with ATI video causes the machine to lock solid (no console, no ssh'ing in, no pinging the box - just have to power cycle) when X attempts to start (although this also happens with Testing, so doesn't really address your question -- stable works fine).
So, yes, there are some practical disadvantages to running unstable vs testing, but for the _most_ part, I believe unstable is a better choice than stable for most desktop users.
-- Kent