From owner-freebsd-current@FreeBSD.ORG Tue Oct 19 14:14:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BDBF16A4CE for ; Tue, 19 Oct 2004 14:14:51 +0000 (GMT) Received: from drop.bsdchat.com (drop.bsdchat.com [209.237.225.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6889543D2D for ; Tue, 19 Oct 2004 14:14:51 +0000 (GMT) (envelope-from clive@tongi.org) Received: from CARTIER (drag.bsdchat.com [209.237.225.37]) by drop.bsdchat.com (8.13.1/8.13.1) with SMTP id i9JEETEh006212; Tue, 19 Oct 2004 14:14:31 GMT (envelope-from clive@tongi.org) Received: (nullmailer pid 1230 invoked by uid 1000); Tue, 19 Oct 2004 14:14:11 -0000 Date: Tue, 19 Oct 2004 22:14:11 +0800 From: Clive Lin To: Andy Hilker Message-ID: <20041019141411.GB929@CARTIER> References: <20041018173820.GB56576@mail.crypta.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041018173820.GB56576@mail.crypta.net> X-Operating-System: FreeBSD i386 X-PGP-key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xA008C03E User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: 5.3-RC1: jail + bind9, devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 14:14:51 -0000 Hi, Here is my 'cheat sheet' for running chrooted bind9 within jail: o First, make sure the the /etc/namedb is correctly symlinked to /var/named/etc/namedb. make distribution (part of jail building process) does _not_ do it rignt. o Assuming your jail is at /d/jails/myjail, and the hostname is myjail, now issue # cd /d/jails/myjail/var/named/dev # mknod random c 245 0; mknod null c 2 2 o finally, put 2 lines in myjail:/etc/rc.conf named_enable="YES" named_chroot_autoupdate="NO" That's all. I've deployed several 5.3 boxes since the frist day bind got chrooted, without noticeable problem. PS, if it's the first time your cute bind9 booting up, run make-localhost and fix named.conf. there's no 127.0.0.1 within jail ;) -- Clive Tong-I Lin | http://tongi.org | PGP KeyID: A008C03E