On Mon, 06 Sep 2010 17:02:23 +0100, Terry Coles <[email protected]>
wrote:
Can anyone point me at a 101 standard tutorial or reference page which
explains how running code gets overwritten in memory when Linux updates
packages?
I think you'll find (someone may correct me soon) that most of the time
the code doesn't get update in the running software.
What tends to happen is you will update (for example) Apache, the files on
disk will be re-written but the old version of the application will
continue to run from memory. Then you will manually reboot Apache.
This doesn't require a reboot as there are no registry values etc. to
update and in general *nix applications manage their memory better and the
kernel manages pages better. Nowadays it is rare for programs to "require"
the reboot. Core Windows updates will require a reboot as it is much
easier to shut the whole machine down and bring all software up fresh,
than to select what bits of the system to refresh.
On *nix systems you tend to find applications are more atomic and keep
themselves to themselves. So an update to your browser does not require
your desktop environment to be restarted.
--
Robert Bronsdon
--
Next meeting: Blandford Forum, Tuesday 2010-09-07 20:00
Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/
How to Report Bugs Effectively: http://bit.ly/4sACa
