-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Jan 30, 2017 at 02:47:41PM -0600, Richard Owlett wrote: > On 01/30/2017 11:49 AM, David Wright wrote: > >On Sun 29 Jan 2017 at 08:58:17 (-0600), Richard Owlett wrote:
[...] > The last time I did any low level coding the 8085 was state of the > art ;/ The key question is likely just what defines "a new > instance". IIRC there were no open caja "windows". Could be > mistaken. In this context "instance" means a running program, with its own address space and (most importantly) its own set of loaded shared libraries. Something you would recognize in the output of "ps" or "top", with its own process ID (PID), yadda, yadda. The borders of the concept are a bit hazy with, on the one side "threads" (one address space, several stacks: whoever had this idea should be tarred & frathered, IMO ;-) -- on the other side the possibility of loading several versions of shared libs in one app or "apps" "consisting" of several processes (youngest, but by far not the only ones: browsers running one separate process per tab and giving that old hat a fancy name like "electrolysis". Yo.) But the core concept is pretty clear. In your case it means: a running caja process won't reload its shared libraries just because you changed them (by refreshing your distro) behind its back. And it might get pretty confused if it did: just imagine a data structre in memory, set up by the old dynlib which changed its layout in the new library's version: hours of fun! regards - -- t -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAliQTSEACgkQBcgs9XrR2kZ4jQCfQ12v1f5jqDm5UycTmGYwzB2P 1wsAn1TBrRrk4GWCX5tGSJ98c9P9OMqN =b31V -----END PGP SIGNATURE-----
