Colin Watson <[EMAIL PROTECTED]> wrote:

On Wed, May 19, 2004 at 10:19:29AM -0500, Michael Kahle wrote:


Wednesday, May 19, 2004 5:14 AM Colin Watson wrote:


I *strongly* recommend against upgrading by cron job. Just don't do it; there are lots of ways it can break.


I have heard this mentioned before. Could you elaborate? Why is this a
problem? Please excuse my inexperience here.



Upgrades require interaction from time to time, such as conffile merges.
Even with packages that use debconf, the defaults you get with the
noninteractive frontend aren't always what you want.


I use cron-apt to do downloads *ONLY* of updated packages overnight. Then, the next day, I do and 'apt-get -u upgrade'. This allows me to see what is going to be upgraded and say 'no' if I don't want to complete the upgrade. This also means that I am present to answer any required questions during the actual update.

This worked great until I was forced to switch ISP and I now get almost nightly disconnects in the middle of the download. I wish there was a decent ISP in my area, but that's what I get for living in the mountains of West Virginia.

Marc Shapiro


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Reply via email to