From owner-freebsd-questions@FreeBSD.ORG  Sun Jan 26 14:25:54 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4BB8533A
 for <freebsd-questions@freebsd.org>; Sun, 26 Jan 2014 14:25:54 +0000 (UTC)
Received: from land.berklix.org (land.berklix.org [144.76.10.75])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id CC5FE1AD9
 for <freebsd-questions@freebsd.org>; Sun, 26 Jan 2014 14:25:53 +0000 (UTC)
Received: from park.js.berklix.net (p5DCBC010.dip0.t-ipconnect.de
 [93.203.192.16]) (authenticated bits=128)
 by land.berklix.org (8.14.5/8.14.5) with ESMTP id s0QEPQPv025018;
 Sun, 26 Jan 2014 14:25:27 GMT (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
 by park.js.berklix.net (8.14.3/8.14.3) with ESMTP id s0QEKcQJ024279;
 Sun, 26 Jan 2014 15:20:38 +0100 (CET) (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
 by fire.js.berklix.net (8.14.5/8.14.5) with ESMTP id s0QEKKMn080851;
 Sun, 26 Jan 2014 15:20:32 +0100 (CET) (envelope-from jhs@berklix.com)
Message-Id: <201401261420.s0QEKKMn080851@fire.js.berklix.net>
To: Frank Leonhardt <frank2@fjl.co.uk>
Subject: Re: Why was nslookup removed from FreeBSD 10?
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://berklix.com BSD Unix Linux Consultants, Munich Germany
User-agent: EXMH on FreeBSD http://berklix.com/free/
X-URL: http://www.berklix.com
In-reply-to: Your message "Sat, 25 Jan 2014 21:03:52 GMT."
 <52E426B8.3080905@fjl.co.uk>
Date: Sun, 26 Jan 2014 15:20:20 +0100
Cc: freebsd-questions@freebsd.org
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Jan 2014 14:25:54 -0000

> 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 <arch@freebsd.org>.

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultant, Munich http://berklix.com
 Interleave replies below like a play script.  Indent old text with "> ".
 Send plain text, not quoted-printable, HTML, base64, or multipart/alternative.