Date: Fri, 6 Dec 2013 14:39:44 +0100 From: Rainer Duffner <rainer@ultra-secure.de> To: Torfinn Ingolfsen <torfinn.ingolfsen@getmail.no> Cc: freebsd-stable@freebsd.org Subject: Re: BIND chroot environment in 10-RELEASE...gone? Message-ID: <20131206143944.4873391d@suse3> In-Reply-To: <20131205193815.05de3829de9e33197fe210ac@getmail.no> References: <529D9CC5.8060709@rancid.berkeley.edu> <20131204095855.GY29825@droso.dk> <alpine.BSF.2.00.1312041212000.2022@badger.tharned.org> <E915D8A5-1CD0-465B-BAD1-59C45C9415F4@gid.co.uk> <20131205193815.05de3829de9e33197fe210ac@getmail.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> 2) that this mess around FreeBSD 10 will not slow the > adoption rate of FreeBSD 10. I don't think so. Only a fraction of my servers ever needed BIND. And where we need it, we're happy to install a port of it (which has a lot of OPTIONS, which I saw for the first time only recently...) I can see the point for somebody who is running dozens of BIND-servers, though. Tracking BIND-updates via freebsd-update was/is probably quite convenient. But, I have to say: if you do a major version upgrade, don't read the release-notes (which will mention the absence of BIND, I assume) and don't do a test-run of the upgrade on a non-critical-system, maybe you shouldn't be running a nameserver at all in the first place. And BIND even less so, IMHO.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131206143944.4873391d>