Date: Sun, 26 Jan 2014 21:53:51 +0000 From: Frank Leonhardt <frank2@fjl.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Why was nslookup removed from FreeBSD 10? Message-ID: <52E583EF.6080007@fjl.co.uk> In-Reply-To: <201401261420.s0QEKKMn080851@fire.js.berklix.net> References: <201401261420.s0QEKKMn080851@fire.js.berklix.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <arch@freebsd.org>. > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E583EF.6080007>