From owner-freebsd-current@FreeBSD.ORG Tue Mar 16 02:19:58 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 6F3AF16A4CE for ; Tue, 16 Mar 2004 02:19:58 -0800 (PST) Received: from smtp.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 75F4243D39 for ; Tue, 16 Mar 2004 02:19:57 -0800 (PST) (envelope-from neuhauser@chello.cz) Received: (qmail 87594 invoked by uid 0); 16 Mar 2004 10:19:56 -0000 Received: from r3al16.mistral.cz (HELO isis.wad.cz) (213.220.229.16) by smtp.dkm.cz with SMTP; 16 Mar 2004 10:19:56 -0000 Received: by isis.wad.cz (Postfix, from userid 1001) id A0D312FDA01; Tue, 16 Mar 2004 11:20:10 +0100 (CET) Date: Tue, 16 Mar 2004 11:20:10 +0100 From: Roman Neuhauser To: Colin Percival Message-ID: <20040316102010.GC1102@isis.wad.cz> Mail-Followup-To: Colin Percival , freebsd-current@freebsd.org References: <6.0.1.1.1.20040316023919.039fa5f0@imap.sfu.ca> <20040316094624.GA1102@isis.wad.cz> <6.0.1.1.1.20040316094749.037ce0a0@imap.sfu.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.0.1.1.1.20040316094749.037ce0a0@imap.sfu.ca> User-Agent: Mutt/1.5.4i cc: freebsd-current@freebsd.org Subject: Re: Nuking parts of the world 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, 16 Mar 2004 10:19:58 -0000 # colin.percival@wadham.ox.ac.uk / 2004-03-16 09:58:36 +0000: > At 09:46 16/03/2004, Roman Neuhauser wrote: > > usr.sbin/nslookup should be part of freebsd-base-bind, not > > freebsd-base, just like dig, host and dnsquery (there's probably > > more). > > I thought about those for quite a while. I ended up deciding that > while they are technically part of bind, the most likely reason why > someone would want to remove bind is if they are replacing the *name > server* with something else (eg, djbdns), and they would probably be > surprised if {nslookup, dig, host, dnsquery} disappeared. The best > solution might be to tag those four as freebsd-base-bind-client... as > I said, this was a one-day hack job with all sorts of rough edges. maybe -bind-server and -bind-clients would fit the bill for both of us. this is about granularity after all. on a related note: most of my djbdns installations are because of the tools, not the servers, and most users of the djbdns servers use the tools (dnsq{,r}, dns{name,ip}, ...) exclusively, judging from the mailing list at least. > > isn't the freebsd- prefix enough? I mean, from the names I would > > expect freebsd-base be a superset of all the freebsd-base-*. > > Well, the ports tree already has "freebsd-games", "freebsd-uucp", > and "freebsd-update"; it might be confusing if the -base- were omitted. > Better to err on the side of verbosity. ok, but then freebsd-base should become freebsd-base-base. (yes, my obsession is symmetry :) -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html