You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article A short introduction to cron-apt:

#9 Re: A short introduction to cron-apt Posted by Anonymous (142.68.xx.xx) on Thu 7 Jun 2007 at 13:52 >>Yes, it can be very tedious to manually review each update batch -- especially if you have several servers -- but that is part of your job when you are running a server. Deal with it!<< This "cope" viewpoint is very limited IMHO. The AUTHORS of the updates should have some way to flag fixes that require reboot, update config files, or otherwise cause the user grief. apt/aptitude/dpkg should have a method of filtering these flagged updates to allow non-flagged fixes to be applied, and flagged fixes to be held back until the user manually approves them. This way, the user can zero in on those fixes that actually need attention, and not be bothered by those that don't. THEN it will be easier to "deal with it!".

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account