On Tue, 18 Mar 2014, Wayne E. Van Loon Sr. wrote:
Most of you probably know this, but what you are talking about is
the difference between static and dynamic linking. When using static
linking, all the libraries needed by the program are inserted into
the executable code. Depending upon the environment on the target
machine, statically linked programs usually run faster, are more
portable, but require more disk and memory space.
Static linking also means that if there's a bug or vulnerability in a
supporting library, every binary compiled against that library has to
be updated individually.
For example, if there were a vulnerability in libcrypt, roughly 300
binaries on one of my CentOS 6 servers would have to be rebuilt,
repackaged, and reinstalled.
--
Paul Heinlein
[email protected]
45°38' N, 122°6' W
_______________________________________________
PLUG mailing list
[email protected]
http://lists.pdxlinux.org/mailman/listinfo/plug
