Ken Moffat wrote:
Now that we have maintenance of the stable kernel, I think we
should point people to the latest incremental release of the same
kernel version. So, if we release a book with 2.6.16.12 and
subsequently 2.6.11.{13,14,15} are released, I'd hate to think that
people would religiously follow the book and not use the later
versions.
Mentioning stable releases has a number of implications:
There is one more problem with the frequency of stable kernel releases: I can no
longer afford maintaining the LiveCD kernel due to traffic costs. Details:
the Makefile in the LiveCD tree should specify the SHA1 sum of the full kernel
tarball. Thus, the only way to get it is to download a full tarball (deltup does
help a bit, but is not very reliable and it is still stupid to download 1.5 MB
of deltup for a 10K patch). But each megabyte costs $0.1 in Yekaterinburg,
Russia. If I follow the LFS book with kernel updates, I will run out of budget
quickly.
Possible solutions:
1) In LFS book, point to linux-2.6.16.tar.bz2 and the "latest file named
patch-2.6.16.x.bz2 downloadable from kernel.org".
2) Let LFS stay with full kernel tarballs, but put a LiveCD specific note in the
README or /etc/issue that the kernel is provided in the form of the base release
plus the official patch.
3) Drop me from the list of LiveCD maintainers.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
