diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2023-10-05 14:33:02 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2023-10-05 14:34:07 +0800 |
| commit | 4d634048a11c1e7f9bdc6bc2cf79d3652e4bade0 (patch) | |
| tree | 5cb3083ec9ca545ac2cb33db585d1d7d110ab6fc | |
| parent | 623081aa93df0ec73c93332103a2c31ec6d29ffa (diff) | |
pkgmgt: Reinstall the same version of Glibc should be safe
| -rw-r--r-- | chapter08/pkgmgt.xml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index 7104d9cba..13d79cfdd 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -69,6 +69,17 @@ it. </para> </listitem> + <listitem> + <para>Reinstalling the same version of Glibc (&glibc-version; for + this release of LFS) with patches should be safe when these patches + do not change ABI and API. When a security vulnerability is found + in Glibc, we often need to apply such a patch to fix the + vulnerability and reinstall Glibc. Consult + <ulink url='&lfs-root;lfs/advisories/'>LFS security + advisories</ulink> if you are alerted for a published Glibc security + vulnerability but unsure about the action to take.</para> + </listitem> + <listitem> <para>If a package containing a shared library is updated, and if the name of the library changes, then any packages dynamically linked to the library must be recompiled, to link against the |