Changes in chapter08/pkgmgt.xml [d11686c:343ab13]
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/pkgmgt.xml
rd11686c r343ab13 1 <?xml version="1.0" encoding=" ISO-8859-1"?>1 <?xml version="1.0" encoding="UTF-8"?> 2 2 <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" 3 3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ … … 57 57 The system will keep working fine thanks to the well-defined interface 58 58 between the kernel and userspace. Specifically, Linux API headers 59 need not be (and should not be, see the next item)upgraded59 need not be upgraded 60 60 along with the kernel. You will merely need to reboot your system to use the 61 61 upgraded kernel.</para> … … 63 63 64 64 <listitem> 65 <para>If the Linux API headers or Glibc need to be upgraded to a newer 66 version, (e.g., from Glibc-2.31 to Glibc-2.32), it is safer to 67 rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild 68 all the packages in their dependency order, we do not recommend 69 it. </para> 70 </listitem> 71 72 <listitem> 73 <para>Reinstalling the same version of Glibc (&glibc-version; for 74 this release of LFS) with patches should be safe when these patches 75 do not change ABI and API. When a security vulnerability is found 76 in Glibc, we often need to apply such a patch to fix the 77 vulnerability and reinstall Glibc. Consult 78 <ulink url='&lfs-root;lfs/advisories/'>LFS security 79 advisories</ulink> if you are alerted for a published Glibc security 80 vulnerability but unsure about the action to take.</para> 65 <para>If Glibc needs to be upgraded to a newer 66 version, (e.g., from Glibc-2.36 to Glibc-&glibc-version;), 67 some extra steps are needed to avoid breaking the system. 68 Read <xref linkend='ch-system-glibc'/> for details.</para> 81 69 </listitem> 82 70
Note:
See TracChangeset
for help on using the changeset viewer.