From owner-freebsd-current Wed Mar 5 16:46: 7 2003 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 3D21837B401 for ; Wed, 5 Mar 2003 16:46:06 -0800 (PST) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE83943FA3 for ; Wed, 5 Mar 2003 16:46:05 -0800 (PST) (envelope-from DougB@freebsd.org) Received: from 12-234-22-23.client.attbi.com ([12.234.22.23]) by rwcrmhc51.attbi.com (rwcrmhc51) with SMTP id <2003030600460505100ioksqe>; Thu, 6 Mar 2003 00:46:05 +0000 Date: Wed, 5 Mar 2003 16:46:04 -0800 (PST) From: Doug Barton To: Philip Paeps Cc: "FreeBSD-Current (E-mail)" Subject: Re: Plea for base system trim In-Reply-To: <20030305232641.GC621@juno.home.paeps.cx> Message-ID: <20030305163732.Y50404@12-234-22-23.pyvrag.nggov.pbz> References: <2F03DF3DDE57D411AFF4009027B8C36704129AE6@exchange-uk.isltd.insignia.com> <20030305015947.M18288@znfgre.tberna.bet> <20030305232641.GC621@juno.home.paeps.cx> Organization: http://www.FreeBSD.org/ X-message-flag: Outlook -- Not just for spreading viruses anymore! MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 6 Mar 2003, Philip Paeps wrote: > Is it actually possible for one to build a custom release without the > ``unnecessary'' BIND bits? I haven't grepped the source, forgive me, > but what does 'NO_BIND=true' actually do? If I were to make a release > like that, would that end me up without resolver as well? It's not as thorough as I think it should be. I plan to get cracking on this now that I've got my ports more or less whipped into shape pre-freeze. > Perhaps a NO_NSLOOKUP flag? ;-) Yeah, I'll add that along with the PIGS_WILL_FLY flag. > I just spotted those flags a few days ago. They're very useful. Good news, thanks. > Now my fiddling with the BIND port is reduced to making stuff live under > /var/namedb instead of /etc/namedb as I like having / mounted read-only > as much as possible. One way you can do this fairly easily with PORT_REPLACES_BASE is to have your chroot tree look something like this: /var/named/ /var/named/etc/namedb/named.conf (etc) Then have /etc/namedb be a symlink to /var/named/etc/namedb, with 'directory "/etc/namedb";' in your named.conf file. That way, both named and ndc "see" the same picture of the system, in and out of the chroot tree. I already use this at work, and I plan to add a lot of this config to the base itself here pretty soon. But you can easily get a head start on it now using what I described above. Doug -- This .signature sanitized for your protection To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message