For the paast few years, up through stable/10, I've had a dedicated "build machine" at home where I build the role-specific kernels for a couple of "production" machines (they "only" at home, but my spouse & I depend on them), and update the production machines by (temporarily) mounting /usr/src and /usr/obj from the build machine onto each production machine (via NFS), then performing (essentially) make installkernel, make installworld, mergemaster (with the usual additional steps).
This has worked quite well, and has been nearly trouble-free. It's described in rather more detail in <http://www.catwhisker.org/~david/FreeBSD/upgrade.html>.) Now, the build machine itself runs a GENERIC kernel (and has minimal ports installed); I told it to build the additional kernels by appending the line: KERNCONF?=GENERIC ALBERT BATS to /etc/src.conf -- and that has been working (as above). Today, as part of my gradual ramp-up toward getting readyto test stable/11 on more than just the above build machine and my laptop, I figured I'd start building those extra kernels (along with GENERIC) when the build machine updated its stable/11. Accordingly, I appended KERNCONF?=GENERIC ALBERT BATS to /etc/src.conf -- but the only kernel even attempted was GENERIC. In reviewing the typescript (as I do all builds within script(1)), there was no indication that the kernel-building process had any awareness that anything other than GENERIC was wanted. Have I managed to overlook something obvious (again)? Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
