Changeset d3b0a08 for chapter08


Ignore:
Timestamp:
01/31/2024 07:31:25 PM (4 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
12.1, 12.1-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.1, xry111/mips64el, xry111/update-glibc
Children:
33a9421, 850536a, cac3cec, d386e51
Parents:
cdf280e
git-author:
Xi Ruoyao <xry111@…> (01/31/2024 05:20:15 PM)
git-committer:
Xi Ruoyao <xry111@…> (01/31/2024 07:31:25 PM)
Message:

pkgmgt: Upgrading Linux API headers cannot be dangerous

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...

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter08/pkgmgt.xml

    rcdf280e rd3b0a08  
    5757        The system will keep working fine thanks to the well-defined interface
    5858        between the kernel and userspace.  Specifically, Linux API headers
    59         need not be (and should not be, see the next item) upgraded
     59        need not be upgraded
    6060        along with the kernel.  You will merely need to reboot your system to use the
    6161        upgraded kernel.</para>
     
    6363
    6464      <listitem>
    65         <para>If the Linux API headers or Glibc need to be upgraded to a newer
     65        <para>If Glibc needs to be upgraded to a newer
    6666        version, (e.g.,  from Glibc-2.31 to Glibc-2.32), it is safer to
    6767        rebuild LFS.  Though you <emphasis>may</emphasis> be able to rebuild
Note: See TracChangeset for help on using the changeset viewer.