diff options
author | Xi Ruoyao <xry111@mengyan1223.wang> | 2021-06-19 16:32:43 +0800 |
---|---|---|
committer | Xi Ruoyao <xry111@mengyan1223.wang> | 2021-06-19 16:32:43 +0800 |
commit | 7aee3182a0bba41d352a50252872ccda2349b8b9 (patch) | |
tree | 50133722dec7a3013c1a35932d62c06820c26817 /chapter08 | |
parent | 577ac46eeac6c240e91ec588f45890c7fced03fb (diff) |
pkg management: add a note about kernel upgrade
Diffstat (limited to 'chapter08')
-rw-r--r-- | chapter08/pkgmgt.xml | 19 |
1 files changed, 15 insertions, 4 deletions
diff --git a/chapter08/pkgmgt.xml b/chapter08/pkgmgt.xml index 809421c3f..228a13378 100644 --- a/chapter08/pkgmgt.xml +++ b/chapter08/pkgmgt.xml @@ -51,10 +51,21 @@ <itemizedlist> <listitem> - <para>If Glibc needs to be upgraded to a newer version, (e.g. from - glibc-2.31 to glibc-2.32), it is safer to rebuild LFS. Though you - <emphasis>may</emphasis> be able to rebuild all the packages in their - dependency order, we do not recommend it. </para> + <para>If Linux kernel needs to be upgraded (for example, from + 5.10.17 to 5.10.18 or 5.11.1), nothing else need to be rebuilt. + The system will keep working fine thanks to the well-defined border + between kernel and userspace. Specifically, Linux API headers + need not to be (and should not be, see the next item) upgraded + alongside the kernel. You'll need to reboot your system to use the + upgraded kernel.</para> + </listitem> + + <listitem> + <para>If Linux API headers or Glibc needs to be upgraded to a newer + version, (e.g. from glibc-2.31 to glibc-2.32), it is safer to + rebuild LFS. Though you <emphasis>may</emphasis> be able to rebuild + all the packages in their dependency order, we do not recommend + it. </para> </listitem> <listitem> <para>If a package containing a shared library is updated, and |