From owner-freebsd-stable@FreeBSD.ORG Tue Dec 3 22:16:34 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4FAA3AE for ; Tue, 3 Dec 2013 22:16:34 +0000 (UTC) Received: from udns.ultimateDNS.NET (ultimatedns.net [209.180.214.225]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id ED72B16E7 for ; Tue, 3 Dec 2013 22:16:33 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id rB3MAYlA053581 for ; Tue, 3 Dec 2013 14:10:40 -0800 (PST) (envelope-from bsd-lists@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id rB3MAT2s053577; Tue, 3 Dec 2013 14:10:29 -0800 (PST) (envelope-from bsd-lists@1command.com) Received: from udns.ultimatedns.net ([209.180.214.225]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Tue, 3 Dec 2013 14:10:29 -0800 (PST) Message-ID: <560e9b24248600b4125c8786712d0bf9.authenticated@ultimatedns.net> In-Reply-To: <20131203.223612.74719903.sthaug@nethelp.no> References: <1386086749.9599.54995173.6CD35E54@webmail.messagingengine.com> <20131203.223612.74719903.sthaug@nethelp.no> Date: Tue, 3 Dec 2013 14:10:29 -0800 (PST) Subject: Re: BIND chroot environment in 10-RELEASE...gone? From: "Chris H" To: freebsd-stable@freebsd.org User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 22:16:34 -0000 >> > It was a deliberate decision made by the maintainer. He said the chroot >> > code in the installation was too complicated and would be removed as a >> > part of the installation clean-up to get all BIND related files out of >> > /usr and /etc. I protested at the time as did someone else, but the >> > maintainer did not respond. I thnk this was a really, really bad >> > decision. >> > >> > I searched a bit for the thread on removing BIND leftovers, but have >> > failed to find it. >> > >> >> You're probably thinking about my November 17 posting: >> http://lists.freebsd.org/pipermail/freebsd-stable/2013-November/075895.html >> >> I'm glad to see others finally speaking up; I was beginning to think I was >> the only one who thought this was not a good idea. I'm a bit surprised >> that no one has responded yet. > > I agree with the protesters here. Removing chroot and symlinking logic > in the ports is a significant disservice to FreeBSD users, and will > make it harder to use BIND in a sensible way. A net disincentive to > use FreeBSD :-( 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? > > Steinar Haug, Nethelp consulting, sthaug@nethelp.no > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >