🚀 go-pugleaf

alan@cjg2.win-uk.net (Alan Talbot) wrote:

>We look after several networks, mostly novell. My boss's approach to
>applying patches and fixes is "If it works, dont fix it", and he
>doesn't believe in applying any unless they are to cure specific
>problems with a particular network. His argument is that the patches
>can introduce further problems and you risk screwing up a working
>network by altering it.

Hi Alan.    Yes, that argument is common and is a good one in many
cases, but I justify (at least to myself) keeping on top of the
trickle of upgrades to our servers as follows - - -

1.  I presume that each patch is the product of many reports from the
field, followed by much research by Novell (who I also presume do not
ENJOY announcing a patch).  So I have no hesitation in learning from
the experience of others, probably a lot like myself.

2.  If Novell thinks I **MIGHT** suffer some errors by NOT upgrading,
and if they DON'T take any money from me for the upgrade - then I'm
delighted to bow to their superior knowledge and experience.   The
documentation with the patch might tell me if it does NOT apply to my
scenario, but unless it is clearly not relevant to my site, Novell
usually recommends applying it.

3.  Stories of problems CAUSED by upgrades are very rare.   So rare I
can't recall the details of any, although I do recall hearing of a
"fixed" patch.

4.  If I do suffer some error and have to call for help, then the
first question Novell (or any other support agent) will ask is "have
you installed the latest patches/upgrades ???      The idea of finding
and applying ALL relevant patches BEFORE starting to fault-find sends
shivers up my back.   Better to apply them in sequence, during some
quiet time when you aren't also struggling with some UN-anticipated
bug.

In spite of all that,  patches are a low-priority item for me and
usually get postponed for some quiet period !!!   But I don't pretend
that I'm immune from the bugs that caused Novell to release them.

Good luck to you and your boss !,    Colin.
--
Colin Pearson   CNA-4
cspea@tcp.co.uk