I also can not recommend the "frequent upgrades" model. When systems would be more stable and less problems would occur at updates, this would be right. But th

I also can not recommend the "frequent upgrades" model. When systems would be more stable and less problems would occur at updates, this would be right. But the reality is simply different. My experience is, that on many updates there are surprises: - software that once was good, just has gone garbage since the last version - some problems with not so common software combinations that was not found from package maintainers - some device drivers that do not cooperate - desktop environments that do no longer support some options as before or just have gone bad - legacy data is not supported by newer application versions or some subtle problems with this data occur ... - .... Also, when upgrades would be possible without hassle and troubles, that model could work -- but it just is not. For example: I wanted to install a newer Ubuntu version on my hosted server. But the automatic upgrade process explicitly says, that it should not be done via a remote session. So for a hosted system, I have to fall back to a complete new install (backup data, fresh install, complete new configuration, re-install backed up data). Also, when you get into trouble, it is not possible to easily go back to the last stable version (in this situation, virtualized systems are very useful). In such a case, it is clear, that I don't want to give up my life to always have the newest stuff on my server. I regret, that OpenBSD is not for me (unless OpenBSD does never suffer from those troubles).