#603 closed defect (wontfix)
Add EXTRAVERSION to Kernel Build Instructions
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Book | Version: | CVS |
Severity: | normal | Keywords: | |
Cc: |
Description
When we build the kernel, we are overlooking a technique that could help a lot of users: using the EXTRAVERSION variable in the kernel's main Makefile.
VERSION=2.4.22
DATE=date +-%Y%m%d
make CC=/opt/gcc-2.95.3/bin/gcc EXTRAVERSION=-lfs$DATE dep
make CC=/opt/gcc-2.95.3/bin/gcc EXTRAVERSION=-lfs$DATE bzImage
make CC=/opt/gcc-2.95.3/bin/gcc EXTRAVERSION=-lfs$DATE modules
make CC=/opt/gcc-2.95.3/bin/gcc EXTRAVERSION=-lfs$DATE modules_install
cp arch/i386/boot/bzImage /boot/linux-${VERSION}-lfs${DATE} cp System.map /boot/System.map-${VERSION}-lfs${DATE}
Add
<note>By using the EXTRAVERSION, the you can do multiple builds of
the same kernel version without overwriting previous builds.
The modules are preserved. Also, the version number is embedded
so that <userinput>uname -r</userinput> gives the matching value
and allows the system to automatically find its first choice for
<filename>System.map</filename> —
<filename>System.map-uname -r
.</filename></note>
Change History (3)
comment:1 by , 21 years ago
Priority: | highest → high |
---|
comment:2 by , 21 years ago
I'll repeat what I said on the list. This is quite a nifty idea. But I feel not suitable for the book. I think it's more suited to a hint.
comment:3 by , 21 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I agree with others, this is a bit too much for the book. I prefer if we stick to the basics of installation. Bruce, would you mind, though, writing a hint about this? Might be good to reference that hint in the book if nothing else?
This is something we can talk about for the next version of LFS.