Date: Tue, 03 Dec 2013 17:05:20 -0800 From: Michael Sinatra <michael@rancid.berkeley.edu> To: Chris H <bsd-lists@1command.com>, freebsd-stable@freebsd.org Subject: Re: BIND chroot environment in 10-RELEASE...gone? Message-ID: <529E7FD0.6060500@rancid.berkeley.edu> In-Reply-To: <560e9b24248600b4125c8786712d0bf9.authenticated@ultimatedns.net> References: <1386086749.9599.54995173.6CD35E54@webmail.messagingengine.com> <CAN6yY1sVGiQFNkoi0mGZs7grJ5SMAui-rDO1e8UDAs0PTUVL9g@mail.gmail.com> <alpine.BSF.2.00.1312031407090.78399@roadkill.tharned.org> <20131203.223612.74719903.sthaug@nethelp.no> <560e9b24248600b4125c8786712d0bf9.authenticated@ultimatedns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/3/13 2:10 PM, Chris H wrote: > > I strongly disagree. The BIND is still available within FreeBSD for anyone who chooses to > use/install it. Further, nothing stops anyone who wishes to continue using the CHROOT(8) > script(s) that provided the BIND with a chroot. Any copy of a FreeBSD-8 (maybe even 9) > install CD/DVD holds all the "magic" required. It is _easily_ acquired, and implemented. In > fact, one could easily turn the whole affair into an automated routine. > So. Bottom line; the BIND still remains with FreeBSD, nothing has been taken away. > The CHROOT(8) scripts are still easily available, and can be implemented, at will, by > anyone who cares to continue using it. > What's the big deal? Indeed, what's the big deal with putting said goop back into the port so that it can be easily installed/maintained by admins? If it's easy to do manually, or to automate by admins, it should be even easier to automate in the port. michael PS. As I already mentioned, your suggestion is exactly what I had already planned to do. I just have no idea if anything I, or anyone else does will be committed back to the port.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529E7FD0.6060500>