🚀 go-pugleaf

In <273@cjg2.win-uk.net>, alan@cjg2.win-uk.net (Alan Talbot) writes:
>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.
>
>I'm not entirely convinced by this argument and I would be
>interested to hear what others think. 
>
>regards,
>
>Alan.
>
>Alan Talbot,  Support Engineer          Phone +44 (0)171 371 8889
>CJG Consultants Ltd.,                   Fax   +44 (0)171 371 9998
>Phoenix House,  Fulham High Street      home  +44 {0}171 221 6738     
>London SW6 3LF                          
>
>
>
>
>
>
>
>
>
>
>
 It's true that a patch can cause problems .This is a reason for not being the first 
to try a patch (let it age a little while before trying it unless you have a specific
problem) .However , a patch is not always to fix an existing problem.It may be 
to avoid a future problem or just to provide better service such as support
for more cdroms in the case of CDROM.NLM.

 You should realize that if you have a problem requiring a call to Novell support
the first question they'll ask after you explain the problem is "Have you applied
the latest patches? NO?? Call us back when you have. Have a good day now!
BYE!" . Keeping your patches up to date will help avoid this situation.