From owner-freebsd-net  Thu Mar 18  8:13:31 1999
Delivered-To: freebsd-net@freebsd.org
Received: from ns1.seidata.com (ns1.seidata.com [208.10.211.2])
	by hub.freebsd.org (Postfix) with ESMTP id E2D0B1542C
	for <freebsd-net@FreeBSD.ORG>; Thu, 18 Mar 1999 08:13:27 -0800 (PST)
	(envelope-from mike@seidata.com)
Received: from localhost (mike@localhost)
	by ns1.seidata.com (8.8.8/8.8.5) with ESMTP id LAA07940;
	Thu, 18 Mar 1999 11:12:55 -0500 (EST)
Date: Thu, 18 Mar 1999 11:12:55 -0500 (EST)
From: <mike@seidata.com>
To: me <onemo@jps.net>
Cc: Leigh Hart <hart@at.dotat.com>, freebsd-net@FreeBSD.ORG
Subject: Re: [Fwd: named message since upgrading to 3.1-Stable]
In-Reply-To: <36F08756.77BC8DA4@jps.net>
Message-ID: <Pine.BSF.4.05.9903181106430.4883-100000@ns1.seidata.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Wed, 17 Mar 1999, me wrote:

> pre-requisite steps needed. Is there anything I obviously missed, or is the
> sandbox configuration broken?

http://www.seidata.com/~mike/papers/named.html

Note, this isn't perfect...  I'm still working out some oddities with
named-xfer's behavior, but it does show the exact steps I took to
chroot named under FreeBSD 3.0-REL.

Later,

					-Mike




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message