[ cc-ed back to debian-isp ] On Tue, Sep 07, 2004 at 09:21:20PM +0300, Ivan Adams wrote: > but how can i understand when there have critical backdoor in some of my > packets in all Debians and need upgrade!
subscribe to the security alert lists and upgrade when advised. you're trying to automate something which should not be automated. > RedHat have client who updates all critical problems automaticaly (or from > Web, but you just say update and that's). I mean how in RedHat all > administrators are sure that their linux is fine after update! if that's all you want then run stable and update from security.debian.org - you'll just get the security updates, which are infrequent. you might occasionally run into the same problem but, given that the security updates are a) backports rather than new versions and b) rare, it's nowhere near as likely as with unstable or testing. with unstable or testing, updated packages will be many and frequent - usually dozens every day. the more packages, the more likely that one of them will need to ask a question, or have a new config file which is incompatible with the previous version, or some other show-stopping problem. > Is that one step back for Debian !? no. i doubt that it works perfectly for RH either. it's not a task that can be completely automated. upgrading requires a skilled person in control of the process. and if you run unstable on production servers (as i do), then you really ought to test all upgrades on other servers or workstations first. the last thing you need is to discover that an upgraded apache or postfix or squid or whatever is broken AFTER you've upgraded it on the server that your users depend upon. craig -- craig sanders <[EMAIL PROTECTED]> The next time you vote, remember that "Regime change begins at home" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
