From owner-freebsd-stable@FreeBSD.ORG  Wed Dec  4 01:05:32 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 0BA2636A
 for <freebsd-stable@freebsd.org>; Wed,  4 Dec 2013 01:05:32 +0000 (UTC)
Received: from burnttofu.net (burnttofu.net [IPv6:2607:fc50:1:9d00::9977])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id C054D119B
 for <freebsd-stable@freebsd.org>; Wed,  4 Dec 2013 01:05:31 +0000 (UTC)
Received: from schuylkill.es.net ([IPv6:2001:400:14:1:e4a6:c53b:b46e:a1a8])
 (authenticated bits=0)
 by burnttofu.net (8.14.7/8.14.5) with ESMTP id rB415Kvk016121
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT);
 Tue, 3 Dec 2013 20:05:22 -0500 (EST)
 (envelope-from michael@rancid.berkeley.edu)
Message-ID: <529E7FD0.6060500@rancid.berkeley.edu>
Date: Tue, 03 Dec 2013 17:05:20 -0800
From: Michael Sinatra <michael@rancid.berkeley.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Chris H <bsd-lists@1command.com>, freebsd-stable@freebsd.org
Subject: Re: BIND chroot environment in 10-RELEASE...gone?
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>
In-Reply-To: <560e9b24248600b4125c8786712d0bf9.authenticated@ultimatedns.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (burnttofu.net [IPv6:2607:fc50:1:9d00::9977]);
 Tue, 03 Dec 2013 20:05:22 -0500 (EST)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 01:05:32 -0000

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.