From owner-freebsd-hackers  Mon Dec  4 13:19:44 2000
From owner-freebsd-hackers@FreeBSD.ORG  Mon Dec  4 13:19:43 2000
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP id C1FE737B400
	for <freebsd-hackers@FreeBSD.ORG>; Mon,  4 Dec 2000 13:19:42 -0800 (PST)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id eB4LJRM46005;
	Mon, 4 Dec 2000 13:19:28 -0800 (PST)
	(envelope-from jkh@winston.osd.bsdi.com)
To: carock@epctech.com
Cc: "FreeBSD Hackers" <freebsd-hackers@FreeBSD.ORG>
Subject: Re: New 4.2 complaint. 
In-Reply-To: Message from "Chuck Rock" <carock@epctech.com> 
   of "Mon, 04 Dec 2000 10:16:29 CST." <001201c05e0d$8ef1f020$1805010a@epconline.net> 
Date: Mon, 04 Dec 2000 13:19:27 -0800
Message-ID: <46001.975964767@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Are you guys on crack? nslookup is still tought as part of basic TCP/IP
> troubleshooting technique, and I think your message about having it removed

I think you're the one on crack - FreeBSD's bundled nslookup doesn't
say anything of the sort.

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message