| Summary: | "make release" custom kernel unsuccessful | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Helmut Schneider <jumper99> |
| Component: | misc | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
State Changed From-To: open->closed This behavior is by design; custom kernels are still available and can be booted off. Here's what the release(7) manpage says about: : KERNELS Specifies a list of additional kernel configura- : tions to compile and install into the ``base'' dis- : tribution. Each kernel is installed into : /boot/<config> so that it can be booted from the : loader via ``boot <config>''. |
Doing a "make release" with a custom kernel fails because when creating boot images the GENERIC kernel is copied instead of the custom kernel. Fix: Just a suggestion, I did not fully test that, but it seems to work... :) [root@orakel /usr/src/release]# diff Makefile.org Makefile 806c806 < @gzip -9nc ${RD}/kernels/GENERIC/kernel > ${RD}/kernels/kernel.gz --- > @gzip -9nc ${RD}/kernels/$(KERNELS)/kernel > ${RD}/kernels/kernel.gz 936,937c936,937 < @echo "Copy GENERIC kernel to boot area" < @cp -Rp ${RD}/kernels/GENERIC/ ${CD_LIVEFS}/boot/kernel --- > @echo "Copy kernel to boot area" > @cp -Rp ${RD}/kernels/$(KENRELS)/ ${CD_LIVEFS}/boot/kernel 1226c1226 < ACPI_KO= ${RD}/kernels/GENERIC/acpi.ko --- > ACPI_KO= ${RD}/kernels/$(KERNELS)/acpi.ko [root@orakel /usr/src/release]# How-To-Repeat: make CHROOTDIR=/home/release CVSROOT=/usr BUILDNAME=6.1-RELEASE RELEASETAG=RELENG_6_1 EXTPORTSDIR=/usr/ports EXTSRCDIR=/usr/src KERNELS_BASE=IBM_HS20_SMP KERNELS=IBM_HS20_SMP NODOC=YES NOPORTS=YES MAKE_ISOS=YES release