> I also have been running "unstable" for a long time now without problem.
> I would say it's the way to go for a non critical personal / hobby use
> machine that has a fast net connection (those update/upgrades are
> usually many tens of MB). In the rare instance (in my experience) where
> anything does go bad, chances are it will be fixed very quickly, or it
> provides a chance to dig into your system and learn a bit about how
> things work together. Another thing to remember is that you don't have
> to upgrade every day. If you like the way your system is working, you
> could keep it in that state as long as you wish - for as long as your
> machine will run if you wish. I usually upgrade every month or so just
> for the sake of it.
I couldn't agree more! I upgrade once or twice a month, usually when I hear some piece of software I like has released, and I want to try out all the new features.
As an experiment, I also gave one machine a cron job to update/upgrade weekly, totally without user intervention. It worked like a dream, except for those times when dependencies shift, or when packages are reorganized, and apt holds them back in order to be sure it doesn't break the system. With some tweaking, though, I think a not-too-critical production server could be made to automagically perform its own security updates. Seems great, considering that certain servers used to require a team of admins to stare at them 24/7.
Levi
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:43:17 EDT