On 2018-08-21 09:23 -0500, Bruce Dubbs wrote:
> On 08/21/2018 04:21 AM, Thomas Trepl wrote:
> > Yes, sure. My thought was that when releasing a book version, we mark
> > some sort of "milestone" and while we are doing that, we know that
> > there are critical bugfixes to one of the most important packages but
> > do not include them. Someone who is building LFS using the stable
> > version 8.3 will miss the fixes if following the written text. Yes we
> > note that there may be newer kernels out there and user should use
> > them, but does it cost us really much to upgrade the kernel version
> > until release date has come?
Yes. Upgrading kernel also upgrades kernel API headers. Then it may break
a package in LFS (very unlikely) or a package in BLFS (eventually). So we
have to revalidate the entire LFS and BLFS.
> Does it make sense to release an -rc every time the kernel changes while
> we are in the middle of validating BLFS? I'll probably update the kernel
> one more time at stable release.
Maybe add notes to tell the audience to update (or patch) the kernel to
mitigate security problems?
6.3.1 Upgrade Issues
+ If the kernel needs to be upgraded, do NOT upgrade kernel API headers.
9.4 What Now?
* Maintenance
+ Recommend to upgrade the kernel regularly for security fixes.
--
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
