From owner-freebsd-security Wed Nov 15 10:38:28 2000 Delivered-To: freebsd-security@freebsd.org Received: from silby.com (cb34181-c.mdsn1.wi.home.com [24.183.3.139]) by hub.freebsd.org (Postfix) with ESMTP id 43B3037B4E5 for ; Wed, 15 Nov 2000 10:38:24 -0800 (PST) Received: (qmail 60875 invoked by uid 1000); 15 Nov 2000 18:38:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 15 Nov 2000 18:38:23 -0000 Date: Wed, 15 Nov 2000 12:38:23 -0600 (CST) From: Mike Silbersack To: Matt Heckaman Cc: Cy Schubert - ITSD Open Systems Group , Kris Kennaway , Evren Yurtesen , freebsd-security@FreeBSD.ORG Subject: Re: BIND Version 8.2.2 patchlevel 7 (Released November 9, 2000) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 15 Nov 2000, Matt Heckaman wrote: > On Wed, 15 Nov 2000, Cy Schubert - ITSD Open Systems Group wrote: > ... > : You must be running an old version of 4.x. Bind 8.2.3-T5B was merged > : into -stable on Jul 3, 2000 and 8.2.3-T6B as MFCed on Nov 2. > > Not quite :) > > I have two machines on 4.1.1-RELEASE, which are new and were installed as > 4.0 originally then upgraded to 4.1.1-RELEASE. The holdback server is > 3.5-STABLE and I simply can't afford to take it down for an upgrade. I'm > not comfortable doing a make world upgrade on 3.5 -> 4.x, mainly because > of the mess it will probably be to clean out old binaries and so forth, > and like I said, downtime on this machine is a huge no-no. The only way > I'd ever consider it is to format and install 4.x clean, then dump the > user info back from tape, but that would take too long.. :) > > * Matt Heckaman - mailto:matt@lucida.qc.ca http://www.lucida.qc.ca/ * > * GPG fingerprint - A9BC F3A8 278E 22F2 9BDA BFCF 74C3 2D31 C035 5390 * Well, as I recall, BIND builds pretty easily on FreeBSD. You could always manually build 8.2.3-T6B if you need it. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message