Date: Wed, 7 Jul 2010 13:53:52 -0700 From: Freddie Cash <fjwcash@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: 8.x grudges Message-ID: <AANLkTin_n_UiUuLRyfEDXaYUpG34n0eC5sBess3aAlzV@mail.gmail.com> In-Reply-To: <4C34E0E6.9070801@aldan.algebra.com> References: <4C34C5DE.7040007@aldan.algebra.com> <20100707185928.GA16180@icarus.home.lan> <4C34E0E6.9070801@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 7, 2010 at 1:17 PM, Mikhail T. <mi+thun@aldan.algebra.com> wrot= e: > 07.07.2010 14:59, Jeremy Chadwick ???????(??): >>> >>> =C2=A0 =C2=A0 =C2=A0FREEBSD_COMPAT7 kernel option is, apparently, a req= uirement (and >>> =C2=A0 =C2=A0 =C2=A0thus not an "option") -- the kernel-config files, t= hat worked with >>> =C2=A0 =C2=A0 =C2=A07.x, break without this option in them (in addition= to all the >>> =C2=A0 =C2=A0 =C2=A0nuisance, that's documented in UPDATING -- which, s= omehow, makes >>> =C2=A0 =C2=A0 =C2=A0the breakage acceptable). config(8) would not warn = about this, but >>> =C2=A0 =C2=A0 =C2=A0kernel build fails. >>> >> >> We don't use this option (meaning it's removed from our kernels). =C2=A0= It's >> definitely not required. =C2=A0All it does is ensure your kernel can >> comprehend executables/binaries built on 7.x. >> > > Attached is the kernel config-file (i386), that worked fine under 7.x. Th= e > kernel-compile will break (some *freebsd7* structs undefined), without th= e > COMPAT_FREEBSD7 option. Try it for yourself... While you may get lucky sometimes, it's very *VERY* rare to be able to re-use a kernel config file across major version releases, at least unchanged. Going from 4.x to 5.x required a new kernel config file. (4.x was my first real install of FreeBSD that was upgraded.) Going from 5.x to 6.x required a new kernel config file. Going from 6.x to 7.x required a new kernel config file. Why do you think going from 7.x to 8.x would be any different? When doing major version upgrades, always start with GENERIC from the new release, and add build your custom config file from there. This is way things have been for many, many, many years. Minor version upgrades (7.x to 7.y) rarely require a new kernel config file, although it's still a good idea to start with GENERIC for the duration of the upgrade. But major upgrades have pretty much always required it. --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin_n_UiUuLRyfEDXaYUpG34n0eC5sBess3aAlzV>