From owner-freebsd-current@FreeBSD.ORG Wed Jan 6 09:05:42 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0A95106566B for ; Wed, 6 Jan 2010 09:05:42 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from host.omnilan.net (host.omnilan.net [62.245.232.135]) by mx1.freebsd.org (Postfix) with ESMTP id 2D3F68FC1F for ; Wed, 6 Jan 2010 09:05:41 +0000 (UTC) Received: from titan.flintsbach.schmalzbauer.de (titan.flintsbach.schmalzbauer.de [172.21.1.150]) (authenticated bits=0) by host.omnilan.net (8.13.8/8.13.8) with ESMTP id o0695b4C045402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 6 Jan 2010 10:05:40 +0100 (CET) (envelope-from h.schmalzbauer@omnilan.de) Message-ID: <4B445257.3080606@omnilan.de> Date: Wed, 06 Jan 2010 10:05:27 +0100 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Thunderbird 2.0.0.23 (X11/20090906) MIME-Version: 1.0 To: Doug Barton References: <4B12CCA8.7050808@omnilan.de> <4B1341E7.1050805@FreeBSD.org> In-Reply-To: <4B1341E7.1050805@FreeBSD.org> X-Enigmail-Version: 0.95.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig278288ABDE7626162557FE28" Cc: freebsd-current@freebsd.org Subject: Re: named, VARMFS=yes and FILESDIR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 06 Jan 2010 09:05:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig278288ABDE7626162557FE28 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Doug Barton schrieb am 30.11.2009 04:54 (localtime): > Harald Schmalzbauer wrote: =2E.. >> while building an embedded slave DNS I recognized that running named o= ut >> of the box with VARMFS enabled would fail. >> Now I could easily fix it for my device only, but I think it's better = to >> solve it upstream. >> VARMFS=3DYes is a standard option, likewise named_enable. >=20 > There are lots of standard options that are not compatible with each > other. Sorry for this long silence. Unfortunately I have only some hours/month=20 spare time to work on this. There are kind of "to be expected" incompatible options, of course, but=20 this one hit me some years before. Especcially for newbies, it's not=20 clear why these options shouldn't work together. >> My idea is to create a namedb directory in /usr/share (like there's on= e >> for sendmail) with duplicate entries of src/etc/namedb >=20 > Why not just set named_chrootdir to /usr/share/namedb ? It's not 100% > clear to me what you're trying to accomplish. Can you please go into a > little more detail about your goals, rather than potential solutions? I think rc.d/var should be able to populate a named compliant /var.=20 Therefore it needs at least named.conf and named.root. My idea was to save them in /usr/share, where many other (sendmail e.g.) = template duplicates also reside. When chrooting to /usr/share/namedb, it = also fails if I don't have the original installed /var, like if /var is=20 a freshly populated memory file system. >> P.S.: named_conf definitions in rc.conf get lost.=20 >=20 > Yes, that's something that needs improvement. I have it on the list > but since it's not common for people to alter the path to the conf > file, and since in the past in order to do so you've had to add -c to > named_flags anyway, I don't regard it as urgent. Is there anything wrong with my patch? Thanks, -Harry --------------enig278288ABDE7626162557FE28 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAktEUmEACgkQLDqVQ9VXb8ixpACghh7eaB7FSY8UiejZu7j/LLHQ /2AAn1w3rA3xpfLhEEvGH7q7Ew4cBmLN =4Y3u -----END PGP SIGNATURE----- --------------enig278288ABDE7626162557FE28--