Re: What is your patch strategy on Sol10 ?
From: Matty (mattyml_at_daemons.net)
Date: 06/07/05
- Next message: Alan Hargreaves - Product Technical Support (APAC): "Re: g++ and solaris 10"
- Previous message: Matty: "Re: x86 Solaris jumpstart client ignoring SjumpsCF values :("
- In reply to: Casper H.S. ***: "Re: What is your patch strategy on Sol10 ?"
- Next in thread: Lion-O: "Re: What is your patch strategy on Sol10 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 06 Jun 2005 22:21:22 -0400
Casper H.S. *** wrote:
> Bruce D Porter <bdp@ytc1.co.uk> writes:
>
>
>>If it ain't broke, don't fix it. (Not just Sol10 , any OS)
>
>
> Modulo security problems, that is.
>
>
>>When installing a new system, patch to the latest levels. Once happy
>>review patches (especially security ones) on a regular basis (say
>>monthly). Apply patches when neccesary, test things still work and if not
>>then back them out.
>
>
> smpatch makes this all too easy :-)
>
> Sun Alerts will keep you informed about security and other important
> issue, and the rest should mostly be driven by problems you find.
>
> Casper
Does this mean the Recommended bundle is no more? I kinda liked getting
all of the latest reliability/security patches in one bundle. Now we
will be required to bundle patches ourselves when we go through the
deployment to dev, qe and production. :(
- Next message: Alan Hargreaves - Product Technical Support (APAC): "Re: g++ and solaris 10"
- Previous message: Matty: "Re: x86 Solaris jumpstart client ignoring SjumpsCF values :("
- In reply to: Casper H.S. ***: "Re: What is your patch strategy on Sol10 ?"
- Next in thread: Lion-O: "Re: What is your patch strategy on Sol10 ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]