Date: Fri, 16 Mar 2018 14:24:06 +0100 From: Polytropon <freebsd@edvax.de> To: Bob McDonald <bmcdonaldjr@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: Removing local_unbound Message-ID: <20180316142406.2b3a7362.freebsd@edvax.de> In-Reply-To: <CAM-YptdAXG-hLEGYewKMnpnLzC-4pX3BuZy1J8i4uny_=BMqEw@mail.gmail.com> References: <CAM-YptdAXG-hLEGYewKMnpnLzC-4pX3BuZy1J8i4uny_=BMqEw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 16 Mar 2018 08:42:59 -0400, Bob McDonald wrote: > > Check "man 5 src.conf". Add > > > WITHOUT_UNBOUND=1 > > > to /etc/src.conf. > > > OK, is there any way to do it that doesn't require rebuilding the system? No. This approach explcitely works _only_ with rebuilding the system. At least once. > This will certainly work but if there are lots of systems, this could get > cumbersome. You can get rid of offending binaries by renaming (or removing) them, or at least removing the +x flag. However, after you've done a freebsd-update, they will be back as they were before. So maybe you can create a script that will perform this task, and then run it after every freeebsd-update. I know this doesn't look right (and it actually isn't), but it will work. I sometimes do this on systems that have base LPR installed, but require CUPS - and then two instances of tools like lpr, lpq or lprm will exist. :-) > Is there something in the install that would leave these programs out? No, this is not intended. The DNS resolver is an essential part of the OS and cannot be removed during the normal installation and updating procedures. Both installation from tarballs and binary updating will install the whole set of OS components onto the system - and doing this manually by "disassembling" this process sounds crazy. :-) But you can wait for "packaged base" to arrive in production and then check if Unbound becomes a package which can be installed optionally (or left out). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180316142406.2b3a7362.freebsd>