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

Edited for style, idiom, and punctuation. Emphasized the need to continue

Browse Source 
applying security patches even after LFS is "complete".
This commit is contained in:
David Bryant 2022-10-21 12:59:34 -05:00
parent 347bbda9c1
commit eaf26ea596
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
prologue/errata.xml
View File

@ -13,18 +13,18 @@
<para>The software used to create an LFS system is constantly being updated <para>The software used to create an LFS system is constantly being updated
and enhanced. Security warnings and bug fixes may become available after and enhanced. Security warnings and bug fixes may become available after
the LFS book has been released. To check whether the package versions or the LFS book has been released. To check whether the package versions or
instructions in this release of LFS need any modifications to accommodate instructions in this release of LFS need any modifications&mdash;to repair
security vulnerabilities or other bug fixes, please visit security vulnerabilities or to fix other bugs&mdash;please visit
<ulink url="&errata;"/> <ulink url="&errata;"/>
before proceeding with your build. You should note any before proceeding with your build. You should note any
changes shown and apply them to the relevant section of the book as you changes shown and apply them to the relevant sections of the book as you
progress with building the LFS system.</para> build the LFS system.</para>
<para>In addition, the Linux From Scratch editors maintain a list of security <para>In addition, the Linux From Scratch editors maintain a list of security
vulnerabilities discovered after a book was released. To check whether there vulnerabilities discovered <emphasis>after</emphasis> a book has been released. To see
are any active security vulnerabilities, please visit whether there are any known security vulnerabilities, please visit
<ulink url="&secadv;"/> prior to proceeding with your build. You should note <ulink url="&secadv;"/> before proceeding with your build. You should also continue
any advisories and perform the steps to fix any security vulnerabilities as to consult the advisories, and fix any security vulnerabilities, even
you progress with building the LFS system.</para> when the LFS system has been completely constructed.</para>
</sect1> </sect1>