Date: Fri, 31 May 2019 23:04:30 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Jamie Landeg-Jones <jamie@catflap.org> Cc: voidanix@420blaze.it, rainer@ultra-secure.de, freebsd-current@freebsd.org Subject: Re: Disabling COMPAT_FREEBSD4/5/6/7/9 as a default kernel option Message-ID: <201906010604.x5164UIl033057@gndrsh.dnsmgr.net> In-Reply-To: <201906010156.x511ufxu051982@donotpassgo.dyslexicfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> rainer@ultra-secure.de wrote: > > > I have a 32bit FreeBSD 6 binary that I'll need for a bit until the > > department who is technically responsible for the service gets around > > redoing that service. > > >From my understanding from reading the bug (though it's not entirely clear > in this thread), this relates to removing the options from the generic (et al.) > kernels, not deleting the code itself. That would make GENERIC less than GENERIC as you can not load these changes as modules, nor would it be easy to make them modules. > You'd therefore be able to just keep the options enabled in your own > config.. , or is this just the first stage of full deprecation? And that too, if you take stuff out of GENERIC it gets built less often and that often leads to bit rot and that often leads to deprecation because it "must not be used it has rotted and look no one has complained." (Which, imho, is a rotton support model.) > Cheers, Jamie -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201906010604.x5164UIl033057>