Date: Tue, 19 Oct 2004 22:14:11 +0800 From: Clive Lin <clive@tongi.org> To: Andy Hilker <ah@crypta.net> Cc: freebsd-current@freebsd.org Subject: Re: 5.3-RC1: jail + bind9, devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device Message-ID: <20041019141411.GB929@CARTIER> In-Reply-To: <20041018173820.GB56576@mail.crypta.net> References: <20041018173820.GB56576@mail.crypta.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041019141411.GB929>