Date: Sun, 29 Sep 2024 13:02:58 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: void <void@f-m.fm> Cc: freebsd-current@FreeBSD.org Subject: Re: Is INET6 a required option these days? (kernel build failure) Message-ID: <202409292002.48TK2wWC093385@gndrsh.dnsmgr.net> In-Reply-To: <ZvljLFZDO8lNk9qy@int21h>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sun, Sep 29, 2024 at 02:13:01PM +0000, Gary Jennejohn wrote: > > >I personally have been using a customized kernel configuration file for > >25 years or more and I have no intention of changing it. > > > >Just because INET6 shows up in all the boilerplate config files doesn't > >change the fact that INET6 is still an option. > > I've always thought inet6 stuff was needed by some internal processes > even if not explicitly enabled. i tried ages ago disabling it all and various > things broke inexplicably, even though I wasn't using it and it wasn't > allowed at the firewall. So, it's like an option, from what I can gather, > but a compulsory one ;) > > I think I'd consider disabling it again if i were making something like > nanobsd. Both INET and INET6 are optional, should always be optional, and breaking that IMHO would be another major flaw in FreeBSD. Yes, occasionally they expereince short term breakage, usually trivilial to fix with a few proper #ifdef's that someone didn't understand they needed. NOT all things need to be network connected! -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202409292002.48TK2wWC093385>