BIND chroot environment in 10-RELEASE...gone?
Harry Schmalzbauer
freebsd at omnilan.de
Mon Jan 5 19:28:20 UTC 2015
Bezüglich Erwin Lansing's Nachricht vom 09.12.2013 12:22 (localtime):
> 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
Unfortunately I don't have time too, but various other mentioned
work-arrounds/replacements isn't what I need/want, personlly.
So I spent some time reenabling auto-chroot, please see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196520
It just works for me, haven't done much testing. Most of the routines
are taken from former base rc.d/named with little tuning.
I hope this helps for the moment.
-Harry
More information about the freebsd-stable
mailing list