gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

pkgmgt: Upgrading Linux API headers cannot be dangerous

Browse Source 
Per a discussion in the team, we only consider an upgradation dangerous
if it may render the system unusable.  "Causing something not able to
build" is never considered dangerous.  Thus upgrading some headers
cannot be dangerous.

The Glibc portion will need an update too (it can be upgraded safely
with some caution) to ease security updates.  But let's do the easy
change first...
This commit is contained in:
Xi Ruoyao 2024-02-01 01:20:15 +08:00
parent cdf280e337
commit d3b0a0842e
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
chapter08/pkgmgt.xml
View File

@ -56,13 +56,13 @@
5.10.17 to 5.10.18 or 5.11.1), nothing else needs to be rebuilt.
The system will keep working fine thanks to the well-defined interface
between the kernel and userspace. Specifically, Linux API headers
need not be (and should not be, see the next item) upgraded
need not be upgraded
along with the kernel. You will merely need to reboot your system to use the
upgraded kernel.</para>
</listitem>
<listitem>
<para>If the Linux API headers or Glibc need to be upgraded to a newer
<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