On 2025-04-21 10:47, Dag-Erling Smørgrav wrote:
Chris <bsd-li...@bsdforge.com> writes:Can I safely move my new kernel to say, kernel.new while running my current kernel as kernel and rebuild the new kernel with the kernconf corrections?If you're booted into kernel.old you can just build a new kernel and run `make reinstallkernel` to replace the new (non-working) kernel without touching kernel.old.
Sorry. But this the first failed kernel in some 40+ years. So I'm now second guessing every move I make... So if I break to the boot prompt and choose boot kernel.old followed by cd /usr/src, make buildkernel KERNCONF=<my-kernel>, make reinstallkernel KERNCONF=<my-kernel> boot -s installworld dance. I'm good to go? Thanks! I really appreciate all the hand holding here. Sorry for all the trouble. --Chris
Same if you're booted into the new kernel with some sort of workaround and want to preserve the old kernel. It is 100% safe to replace or rename the kernel and modules, even the one you're currently running. Just be aware that you may have trouble loading modules afterward. If for instance you boot into kernel.old and then rename /boot/kernel.old to /boot/kernel.works as I suggested earlier, you won't be able to load kernel modules until you update `kern.bootfile` to point to the new location of the running kernel (`make installkernel` does this when it renames the running kernel to kernel.old). DES
-- sent from hardware written from and running on FreeBSD
0xE512722F.asc
Description: application/pgp-keys
