BIND chroot environment in 10-RELEASE...gone?

[Mark Felder]

On Dec 3, 2013, at 18:43, Mark Andrews <marka at isc.org> wrote:

> 
> In message <1386093454.2626.55043181.26E90FA5 at webmail.messagingengine.com>, Mark Felder writes:
>> On Tue, Dec 3, 2013, at 11:40, Michael Sinatra wrote:
>>> 
>>> I am going to put as many of the bits together as I can to see if I can
>>> recreate the chroot environment via a port on 10.0-RELEASE.  I'll also
>>> submit a PR.  But I agree with the others that this is not a good idea,
>>> and if I had known that the port would remove support for chroot, I
>>> would have vigorously protested the switch to unbound.
>>> 
>> 
>> There was no alternative; we couldn't keep BIND in base. BIND 9 will
>> certainly have a EoL before the EoL of FreeBSD 10.x, and we can't use
>> BIND 10 because it requires importing Python to base.
> 
> We, ISC, don't know when BIND 9 will stop being supported so I fail
> to see how FreeBSD can *know* this.  We have committed to 9.9.x
> being supported through June 2017.  I suspect the last 9.X will
> also be supported at least that long as well.

Sorry, this wasn’t completely clear to me. I was under the impression that someone in the project had knowledge that 9.x was on a short leash and that was a part of the decision making process. Maybe an upgrade to the latest 9.x release would have been less painful; I don’t know. Thanks for the information.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20131203/0baba581/attachment.sig>