aboutsummaryrefslogtreecommitdiffstats
path: root/chapter08/pkgmgt.xml
diff options
context:
space:
mode:
Diffstat (limited to 'chapter08/pkgmgt.xml')
-rw-r--r--chapter08/pkgmgt.xml15
1 files changed, 15 insertions, 0 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml
index 228a13378..43b9c57d3 100644
--- a/chapter08/pkgmgt.xml
+++ b/chapter08/pkgmgt.xml
@@ -121,6 +121,21 @@
and rerun that command to confirm nothing is still using the
deleted libraries.
</para></listitem>
+
+ <listitem>
+ <para>If a binary or a shared library is overwrote, the processes
+ using the code or data in the binary or library may crash. The
+ correct way to update a binary or a shared library without causing
+ the process to crash is: remove it first, then install the new
+ version into position. The <command>install</command> command
+ provided by <application>Coreutils</application> has already
+ implemented this and most packages use it to install binaries and
+ libraries. So you won't be troubled by this issue most of the time.
+ However, the install process of some packages (notably Mozilla JS
+ in BLFS) just overwrites the file if it exists and causes crash, so
+ it's safer to save your work and close unneeded running processes
+ before updating a package.</para>
+ </listitem>
</itemizedlist>
</sect2>