Opened 14 years ago
Closed 14 years ago
#2748 closed task (fixed)
Few mismatches around kernel name in chapter 8 of LFS-BOOK-6.6.pdf
Reported by: | A.S | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.7 |
Component: | Book | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description
Few mismatches around kernel name in chapter 8 of LFS-BOOK-6.6.pdf
Mismatch N1 in sections "8.3.3. Contents of Linux"
Original line (mismatch form): "Installed files: config-2.6.32.8, lfskernel-2.6.32.8, and System.map-2.6.32.8"
should be changed to the correct form: "Installed files: config-2.6.32.8, vmlinux-2.6.32.8-lfs-6.6, and System.map-2.6.32.8"
because:
- section "8.3.1. Installation of the kernel" say:
The filename below can be changed to suit your taste, but the stem of the filename should be vmlinux to be compatible with the automatic setup of the boot process described in the next section. The following command assumes an x86 architecture: cp -v arch/x86/boot/bzImage /boot/vmlinux-2.6.32.8-lfs-6.6
- original line (mismatch form in 8.3.3.) followed by "Short Descriptions", where is vmlinux-2.6.32.8-lfs-6.6 (but
not a lfskernel-2.6.32.8) descripted.
Mismatch N2
In section "8.4.2. Setting Up the Configuration" for contents of /boot/grub/grub.cfg wrongly printed menuentries "GNU/Linux, Linux 2.6.30.2-lfs65"* from previous version of LFS, mismatching to /boot/vmlinux-2.6.32.8-lfs-6.6 in the same print and to the actions of above sections of LFS6.6. (Possible reason of mistake somwhere near error inside xml-version error (see http://wiki.linuxfromscratch.org/lfs/browser/trunk/BOOK/chapter08/grub.xml), where hardcoded "Linux 2.6.30.2-lfs65", instead it should be something like ""Linux &linux-&version" as it already done there for "linux /boot/vmlinux-&linux-version;-lfs-&version; root=/dev/sda2 ro single")
P.S. Btw, may be vmlinuz-2.6.32.8-lfs-6.6 instead of vmlinux-2.6.32.8-lfs-6.6 will be more closer to some linux naming traditions, if "cp -v arch/x86/boot/bzImage /boot/vmlinux-2.6.32.8-lfs-6.6" command involved?
i.e. if "bzImage" means "big ZIPed (compressed) Image", then 'z' in vmliuz will illustrate it, especialy according to the some purposes of LFS ("learning experience" and "power that information and knowledge truly bring" (see the Audience section of book ;))
Change History (4)
follow-up: 3 comment:1 by , 14 years ago
comment:2 by , 14 years ago
Milestone: | → 6.7 |
---|---|
Version: | → SVN |
comment:3 by , 14 years ago
Replying to bdubbs@…:
Check if the changes you suggest are in the latest svn book. I did fix the lfskernel->vmlinux issue.
Current ticket progress: 1/3 of suggestions aplied by changes in latest SVN-20100906: "Mismatch N1" closed (fixed).
Remained to fix: "Mismatch N2". In first approximations, it's easy to fix with &linux-&version instead of current plain text (instead hardcoded).
Remained to discuss and, as result, to add (to the book) changes and/or educational explanation: renaming compiled kernel image to vmlinux-* (but not to vmlinuz-*) - is it a mismatch or it's a conceptual selection of LFS editors, those rejecting vmlinuz?
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Fixed at revision 9376. Leaving kernel filename alone because there is no real significance to the naming convention and 'linux' is pretty clear.
We won't go back and fix 6.6 now that 6.7-rc1 has been released, especially for minor text inconsistencies.
Check if the changes you suggest are in the latest svn book. I did fix the lfskernel->vmlinux issue.
Leaving open for now.