Peter Valdemar Mørch wrote:
Ok, but what is the alternative? I find that without dist-upgrade, I
end up with a constantly growing number of packages in the
"The following packages have been kept back"
category.
Jamming dist-upgrade into a cron job will cause problems when a package
doesn't upgrade cleanly.. for example mysql is getting upgraded, the
server will stop and not come back up. Even worse if a kernel upgrade
doesn't create the initrd correctly.. basically too much is going on and
someone should be checking on it.
I don't think apt is meant to be automated. Updating package lists and
pre-caching the packages you'll need later with cron-apt speeds things
up though. The best option would be to use one of the applications other
people have mentioned to *manage* mass updates. The ideal solution is to
sit down once a week, manage an update and have the result propagate to
your machines. Looking at the screenshots, fai seems to do exactly this.
RHEL has a web-based system that does exactly the same but at a price. :P
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
