From owner-freebsd-questions@FreeBSD.ORG Sun Jan 26 21:53:50 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8ABB608 for ; Sun, 26 Jan 2014 21:53:50 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6F1A11F6B for ; Sun, 26 Jan 2014 21:53:50 +0000 (UTC) Received: from [192.168.1.35] (host86-163-127-175.range86-163.btcentralplus.com [86.163.127.175]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s0QLrmkT060385 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 26 Jan 2014 21:53:48 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52E583EF.6080007@fjl.co.uk> Date: Sun, 26 Jan 2014 21:53:51 +0000 From: Frank Leonhardt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Why was nslookup removed from FreeBSD 10? References: <201401261420.s0QEKKMn080851@fire.js.berklix.net> In-Reply-To: <201401261420.s0QEKKMn080851@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jan 2014 21:53:51 -0000 On 26/01/2014 14:20, Julian H. Stacey wrote: >> There must be a discussion about how the decision was taken somewhere, >> mustn't there? If there isn't, its looking like an accident. >> >> Regards, Frank. > Hi Frank & questions@, > There were discussions. Nslookup was treated as a corollary of > removing bind from src/ to ports/. To find discussions search archives > with word bind in subject headers, (better than keyword nslookup or named). > I recall archives to search as current@ or stable@ freebsd.org. > > The rationale for bind removal from src/ I thought ill advised; it won't > suprise me if FreeBSD gets roasted for no longer being net server ready. > > Complaints or calls for review should go to . > > Cheers, > Julian Thanks - I'm following this up. Incidentally, I've tested it and nslookup /runs/ just fine without any other part of BIND being present. Regards, Frank.