Improper handling of -p ${pidfile} in lfs-bootscripts
DJ Lucas
dj at linuxfromscratch.org
Wed Mar 26 00:30:31 MDT 2008
Alexander E. Patrakov wrote:
> Dan Nicholson wrote:
>> The problem is, for BLFS-6.3, we have to rely on the bootscripts from
>> LFS-6.3, which have this bug.
>
> No. We can (and, IMHO, should) release LFS-6.3.1 right now, with this fix and
> GRUB patch to fix incompatibility with the new e2fsprogs that may be present in
> the latest distros.
>
Dan's patch hasn't been committed yet, but AFAICT, it is safe. I don't
use those scripts anymore. As far as releasing a new LFS, I don't know.
If it were only bootscripts, I'd do an errata entry, and add a
reminder to the blfs-bootscripts page.
However, it seems to me that if LFS hasn't released say every (insert a
responsible value here - 6?) months, if there is errata, a new tiny
release should be made. It's not like it takes all that much to modify
a released book from it's own svn branch--I mean all the hard work is
done already. Proofreading, testing, instruction verification, test
suite results, SBU timings, etc. should still be good.
-- DJ Lucas
More information about the lfs-dev
mailing list