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

[Greg Rivers]

On Mon, 9 Dec 2013, Erwin Lansing wrote:

> On Thu, Dec 05, 2013 at 11:34:31AM -0600, Greg Rivers wrote:
>> On Thu, 5 Dec 2013, Erwin Lansing wrote:
>>>
>>> Thanks Greg, and thanks for the feedback.  I did make sure that the 
>>> chroot still is supported on existing 8 and 9 systems, so the move 
>>> will be another part in the upgrade procedure to a new major release 
>>> and lessen the pain a bit.  Let me have another look into 
>>> reintroducing the chroot bits in a less complicated way.  It may not 
>>> be exactly the same as before but hopefully can be done in a backwards 
>>> compatible way.
>>>
>>
>> Thank you Erwin.  Let me know if I can help in any way.
>>
>
> Sorry for the delay.  I've spent too much time already on this.  The 
> problem is that there are several assumption to how the paths are formed 
> in both the ports Makefile (and thus things like pkg-plist and used to 
> generate the configuration files) and the rc script that sets up the 
> chroot.  Fixing one, breaks the other, so some more magic is required. I 
> hacked up the original chroot code enough that it sets up the chroot, 
> copies in the confiruation files, etc. but then ends up that the 
> configuration files were generated on the assumption that is was a 
> normal port prefix and thus expect things to be in 
> /var/named/usr/local/etc/named/... which is of course a fine chroot, but 
> not compatible with the pre-10 setup.
>
> I think a complete rewrite is needed to do this right, for which I don't 
> have time over the next few days.  The net/isc-dhcp*-server ports might 
> have some inspiration, though not sure how transferrable it is to bind. 
> I'd be happy to test and accept patches.
>

I'll look into it.  Thanks.

-- 
Greg