-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/12/11 10:38, Sthu Deus wrote:
> Thank You for Your time and extended answer, Joe:
>
>> The general rule of thumb is to automatically update only workstations
>> and test servers, never production servers.
>>
>> There is no way that automation ca
On Tue, Dec 13, 2011 at 03:35:37PM +0700, Sthu Deus wrote:
> Good time of the day.
>
>
> I have put to cron auto update of a system by aptitude.
>
> As parameters I set safe-upgrade and 'yes' to all questions - so that
> packages might be installed itself in case of config. questions, etc.
>
>
Hello Sthu,
Thank You for Your time and extended answer, Joe:
The general rule of thumb is to automatically update only workstations
and test servers, never production servers.
There is no way that automation can know whether it is wise to apply a
particular update immediately, to wait a whil
Thank You for Your time and extended answer, Joe:
>The general rule of thumb is to automatically update only workstations
>and test servers, never production servers.
>
>There is no way that automation can know whether it is wise to apply a
>particular update immediately, to wait a while, or not d
On Tue, 13 Dec 2011 15:35:37 +0700
Sthu Deus wrote:
> Good time of the day.
>
>
> I have put to cron auto update of a system by aptitude.
>
> As parameters I set safe-upgrade and 'yes' to all questions - so that
> packages might be installed itself in case of config. questions, etc.
>
> Now I
Good time of the day.
I have put to cron auto update of a system by aptitude.
As parameters I set safe-upgrade and 'yes' to all questions - so that
packages might be installed itself in case of config. questions, etc.
Now I think it will not be secure in case there is a problem w/ public
key of
6 matches
Mail list logo
