Date: Wed, 2 Jan 2019 20:01:24 -0500 From: Robert Huff <roberthuff@rcn.com> To: John Baldwin <jhb@FreeBSD.org> Cc: Robert Huff <roberthuff@rcn.com>, current@freebsd.org Subject: Re: kernel config question Message-ID: <23597.24292.297840.309399@jerusalem.litteratus.org> In-Reply-To: <162e2013-9181-50cd-a3aa-8231e0a1eb99@FreeBSD.org> References: <23597.4315.739853.729163@jerusalem.litteratus.org> <20190102200226.GQ84895@home.opsec.eu> <792fec6e-2dcc-3fba-73d7-31e925cf2a13@FreeBSD.org> <23597.11683.194179.304498@jerusalem.litteratus.org> <162e2013-9181-50cd-a3aa-8231e0a1eb99@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin writes: > - [8] In order to have a kernel that can run the 4.x binaries needed to > - do an installworld, you must include the COMPAT_FREEBSD4 option in > - your kernel. Failure to do so may leave you with a system that is > - hard to boot to recover. A similar kernel option COMPAT_FREEBSD5 is > - required to run the 5.x binaries on more recent kernels. And so on > - for COMPAT_FREEBSD6 and COMPAT_FREEBSD7. > + [8] The new kernel must be able to run existing binaries used by > + an installworld. When upgrading across major versions, the new > + kernel's configuration must include the correct COMPAT_FREEBSD<n> > + option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x > + binaries). Failure to do so may leave you with a system that is > + hard to boot to recover. A GENERIC kernel will include suitable > + compatibility options to run binaries from older branches. Maybe not perfect, but _much_ better. Thanks. Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23597.24292.297840.309399>