Operational system updates

From: Dr. A. Golovanov <A.Golovanov_at_umist.ac.uk>
Date: Mon, 09 Dec 2002 16:57:24 +0000

Hi,
I've got philosophic question after one of the programs stopped working for
unknown reasons (bug, obviously) following operational system update :(

Does anybody use any particular strategy to avoid potential problems with
incompatibility of existing programs, especially those running
spectrometers (like Xwinnmr, etc., which are not updated as often as OS)
and new updates of operational system (e.g., for minor updates from
IRIX6.5.N to 6.5.N+1, or major updates from 6.N to 6.N+1)? If you do
update OS, you are risking to introduce incompatibilities or introduce new
bugs into otherwise perfectly running system (and then wait for couple of
weeks until the bug will be found and fixed). If you do not update OS, you
risk to compromise security. Personally I would rather keep the working
system as it is while it works, and update only as last resort, but may be
I'm paranoid?
Any suggestions on this issue? I wonder if it is possible to keep up with
security improvements, but without many changes in the system.

I'll digest the answers and put them to AMMRL.

Best regards,
Alex



--
    Dr. Alexander P. Golovanov
    Biological Magnetic Resonance Centre
    Department of Biomolecular Sciences
    University of Manchester Institute of Science & Technology (UMIST)
    P.O.Box 88,
    Manchester M60 1QD
    Tel. No: ++44 (0) 161 200 5813  Office
                ++44 (0) 161 200 5812  NMR room
    Fax. No: ++44 (0) 161 236 0409
    e-mail a.golovanov_at_umist.ac.uk
Received on Mon Dec 09 2002 - 18:10:54 MST

This archive was generated by hypermail 2.4.0 : Mon Jun 05 2023 - 17:06:11 MST