From owner-freebsd-stable@FreeBSD.ORG Tue Dec 3 09:40:42 2013 Return-Path: Delivered-To: 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 D15E8258 for ; Tue, 3 Dec 2013 09:40:42 +0000 (UTC) Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB4C41365 for ; Tue, 3 Dec 2013 09:40:42 +0000 (UTC) Received: by mail-pd0-f176.google.com with SMTP id w10so19777041pde.35 for ; Tue, 03 Dec 2013 01:40:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=95JXnkYuLNiuZ8hZ7JObkM2VfmDpJiHH3ueam6wmCSc=; b=mt4MaaCxdii8HW5sSUaMDXE5oekZh832Wt7rKRB7v9mWbCXMhh0x/1PUQgfdNmS+g0 NbYd0xyYSErg9cDlrPhKWQcH43iJf3dJdKyYkaiuTJmYIjDAqinWhmX9pVGP6zIeraHb zro8n91qFwgP5geQN2040q+DY736L6lasmRLkjDOqvNPVXY8+nzzyl594AYjm609zPOF XP2x1ZbEcJN2r4cF/HAnz7kdW5Lff3qQKWBNy8WLQRJ2LOpimCjEZza96mb9FlqCRUF/ c4FiDUB25n/E1if8j0iUtA6c3slFmDMkQ/K1c9CAf+xfcYL2M0u8iaw15OWLkHRgEalT LLqQ== MIME-Version: 1.0 X-Received: by 10.66.158.99 with SMTP id wt3mr53090045pab.113.1386063642353; Tue, 03 Dec 2013 01:40:42 -0800 (PST) Received: by 10.66.142.167 with HTTP; Tue, 3 Dec 2013 01:40:42 -0800 (PST) In-Reply-To: <529D9CC5.8060709@rancid.berkeley.edu> References: <529D9CC5.8060709@rancid.berkeley.edu> Date: Tue, 3 Dec 2013 10:40:42 +0100 Message-ID: Subject: Re: BIND chroot environment in 10-RELEASE...gone? From: Zenny To: Michael Sinatra Content-Type: text/plain; charset=ISO-8859-1 Cc: stable@freebsd.org 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 09:40:42 -0000 +1 On 12/3/13, Michael Sinatra wrote: > I am aware of the fact that unbound has "replaced" BIND in the base > system, starting with 10.0-RELEASE. What surprised me was recent > commits to ports/dns/bind99 (and presumably other versions) that appears > to take away the supported chroot capabilities. OTOH, it appears that > unbound has been given these capabilities. > > I have no issues with removing BIND from base, but taking away the very > robust chroot support that FreeBSD had for BIND is something I would > oppose. I like the idea of leveling the playing field for users of > other systems, but the way things have been implemented thus far--taking > away functionality from BIND while preferring unbound--seems > counter-productive. It doesn't really level the playing field, it just > turns it the other way. > > It seems like it would be pretty easy to preserve the /etc/rc.d/named > startup script and BIND.chroot.dist from 9.x and add them to the BIND > ports, so that people who need to run a full-blown BIND installation can > "just install the port" as was advised back in 2012 when the > BIND/unbound change was first being discussed on -hackers. What are the > obstacles to doing something like this? > > michael > _______________________________________________ > 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" >