new BIND releases today
Fresh out of the oven: BIND 9.3.0 BIND 9.2.4 BIND 8.4.5 For more information, see: http://www.isc.org/sw/bind/ http://www.isc.org/sw/bind/bind9.3.php Joe
Joe Abley wrote:
Fresh out of the oven:
BIND 9.3.0 BIND 9.2.4 BIND 8.4.5
For more information, see:
http://www.isc.org/sw/bind/ http://www.isc.org/sw/bind/bind9.3.php
"Known Defects in BIND 9.3.0: <snip> * named.conf(5) is being installed in the wrong location." Humm... kwalidee koding there ;-) -- Juha
Juha wrote:
Joe Abley wrote:
*SNIP*
"Known Defects in BIND 9.3.0:
<snip> * named.conf(5) is being installed in the wrong location."
Humm... kwalidee koding there ;-)
It's a safety feature. They're making sure they don't over-write your existing named.conf file. I think it's most considerate of them, actually :P -- Matthew Poole Lower Hutt, NZ "Three pills a day keeps the voices at bay" Matthew Poole
Matthew Poole wrote:
Juha wrote:
Joe Abley wrote:
*SNIP*
"Known Defects in BIND 9.3.0:
<snip> * named.conf(5) is being installed in the wrong location."
Humm... kwalidee koding there ;-)
It's a safety feature. They're making sure they don't over-write your existing named.conf file. I think it's most considerate of them, actually :P
isnt it the named.conf man file? :O if its the named.conf file then... yea... :( -- Antonio Broughton W: http://www.flerwin.net J: worzeel(a)jabber.org.nz
On Fri, 24 Sep 2004, Antonio Broughton wrote:
Matthew Poole wrote:
Juha wrote:
* named.conf(5) is being installed in the wrong location."
isnt it the named.conf man file? :O if its the named.conf file then... yea... :(
Oh, yeah, whoops. That'll learn me for posting before I've had my morning coffee. That is pretty slack, really. One wonders if they knew before release.
On 23 Sep 2004, at 17:27, Matthew Poole wrote:
That is pretty slack, really. One wonders if they knew before release.
It was known before release (9.3 shipped with that list of known defects). It's not so much slack, or sloppy coding, as disciplined release engineering. Fixing that bug before release would have required a new release candidate, which would have needed to proceed through internal testing, BIND Forum testing and then public testing, all of which would probably have put back the release another two weeks. Since the named.conf manual page doesn't contain anything much of use anyway (all the BIND documentation lives in the Administrator's Reference Manual, and the manual pages are really just pointers to that) this didn't seem like a reason to delay the release. If there had been bugs with CERT-worthy security issues in them found in the final release candidate, the code would not have been released. The items in the "known defects" list fall well below that bar. Joe
On Thu, Sep 23, 2004 at 05:47:47PM -0400, Joe Abley wrote:
On 23 Sep 2004, at 17:27, Matthew Poole wrote:
That is pretty slack, really. One wonders if they knew before release.
It was known before release (9.3 shipped with that list of known defects).
It's not so much slack, or sloppy coding, as disciplined release engineering. Fixing that bug before release would have required a new release candidate, which would have needed to proceed through internal testing, BIND Forum testing and then public testing, all of which would probably have put back the release another two weeks.
I wonder if they rushed it to fit in with the FreeBSD 5.3 release, Bind 9.3 has just been imported into RELENG_5.
On 23 Sep 2004, at 19:39, Andrew Thompson wrote:
I wonder if they rushed it to fit in with the FreeBSD 5.3 release, Bind 9.3 has just been imported into RELENG_5.
ISC has lots of contact with the FreeBSD people (we use it extensively ourselves, and we also host ftp.freebsd.org and cvsup.freebsd.org), and we knew that the FreeBSD people were hoping to squeeze BIND 9.3 into FreeBSD 5.3-REL. There are lots of other vendors (commercial and otherwise) who ship BIND as part of their operating systems, and presumably we hit one or two of their commit deadlines as well. BIND 9.3 has been in the works, after all, for a long time. However, 9.3 was not rushed out the door to suit the timing of any other project. The fact that it arrived in time to be committed in RELENG_5 is just a happy coincidence for people who run BIND on FreeBSD. Joe
participants (5)
-
Andrew Thompson -
Antonio Broughton -
Joe Abley -
Juha Saarinen -
Matthew Poole