Re: kernel config question
On 1/3/19 10:40 PM, Kevin Oberman wrote: > On Wed, Jan 2, 2019 at 5:02 PM Robert Huff wrote: > >> >> 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 >>> +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 >> > Some ports may require compat ports. E.g. plexmediaserver requires > compat9x. Oddly, compat9x requires compat10x, so I need 9, 10, and 11. > > Now that 10 is EOL, I wish Plex would start building their blobs against 11. While that is true, that isn't quite relevant to this note which is specific to the buildworld + installworld upgrade process. In general COMPAT_FREEBSD and the compatx packages require all the newer compat options and packages when you are more than 1 branch away from the running system. That is, to run 9.x binaries on a 12.0 kernel you need COMPAT_FREEBSD9, COMPAT_FREEBSD10, and COMPAT_FREEBSD11. The same can be true of compat packages except that you only need to step up to whatever the verison of your userland binaries are. If you had a 9.x jail on a 12.0 host you wouldn't need any compat packages, just the kernel options. For a 10.x jail on a 12.0 host you would only need compat9x, etc. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
On Wed, Jan 2, 2019 at 5:02 PM Robert Huff wrote: > > 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 > > +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 > Some ports may require compat ports. E.g. plexmediaserver requires compat9x. Oddly, compat9x requires compat10x, so I need 9, 10, and 11. Now that 10 is EOL, I wish Plex would start building their blobs against 11. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
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 > +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 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
On 1/2/19 1:31 PM, Robert Huff wrote: > > 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. [...] >> >> > No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed. >> >> Yes, that text needs to be made more generic to say that you will need >> COMPAT_FREEBSD. Though we've also had some major branches that >> didn't get a COMPAT_FREEBSD option. > > Are any of those still supported? I'm not sure, but I mean more that you can't assume we will always have a COMPAT_FREEBSD. There was a COMPAT_FREEBSD11. It looks like we actually only skipped COMPAT_FREEBSD8 to date. Perhaps we can just avoid worrying about the lack of COMPAT_FREEBSD. The text does say "and so on" for newer versions, but it's probably not clear. How about this: Index: UPDATING === --- UPDATING(revision 342703) +++ UPDATING(working copy) @@ -1901,12 +1901,13 @@ COMMON ITEMS: can be deleted by "make delete-old-libs", but you have to make sure that no program is using those libraries anymore. - [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 + 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. Make sure that you merge any new devices from GENERIC since the last time you updated your kernel config file. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
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. [...] > > > No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed. > > Yes, that text needs to be made more generic to say that you will need > COMPAT_FREEBSD. Though we've also had some major branches that > didn't get a COMPAT_FREEBSD option. Are any of those still supported? Curiously, Robert Huff ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
On 1/2/19 12:02 PM, Kurt Jaeger wrote: > Hi! > >> FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64 >> >> to CURRENT (as of last midnight. >> Does this, in src/UPDATING: >> >> [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. [...] > >> (It seems ... irrational ... one would need compatibility stuff >> going back to FreeBSD 4 to rebuild/update FreeBSD 13.) > > No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed. Yes, that text needs to be made more generic to say that you will need COMPAT_FREEBSD. Though we've also had some major branches that didn't get a COMPAT_FREEBSD option. -- John Baldwin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: kernel config question
Hi! > FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64 > > to CURRENT (as of last midnight. > Does this, in src/UPDATING: > > [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. [...] >(It seems ... irrational ... one would need compatibility stuff > going back to FreeBSD 4 to rebuild/update FreeBSD 13.) No, COMPAT_FREEBSD4 is not needed. Maybe COMPAT_FREEBSD11 is needed. -- p...@freebsd.org +49 171 3101372 One year to go ! ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
kernel config question
I'm updating a machine from: FreeBSD 12.0-CURRENT #0 r331659: Thu Mar 29 12:31:36 EDT 2018 amd64 to CURRENT (as of last midnight. Does this, in src/UPDATING: [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. still apply? (It seems ... irrational ... one would need compatibility stuff going back to FreeBSD 4 to rebuild/update FreeBSD 13.) Respectfully, Robert Huff ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
