From owner-freebsd-current  Mon Nov 17 19:36:01 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA12205
          for current-outgoing; Mon, 17 Nov 1997 19:36:01 -0800 (PST)
          (envelope-from owner-freebsd-current)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA12196
          for <current@freebsd.org>; Mon, 17 Nov 1997 19:35:57 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.210.252] 
	by pop.uniserve.com with smtp (Exim 1.73 #1)
	id 0xXeS8-0001at-00; Mon, 17 Nov 1997 19:35:53 -0800
Date: Mon, 17 Nov 1997 19:35:49 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Adam McDougall <mcdougall@ameritech.net>
cc: current@freebsd.org
Subject: Re: teardrop
In-Reply-To: <3470F4B7.2AC390D0@ameritech.net>
Message-ID: <Pine.BSF.3.96.971117193518.9470A-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Mon, 17 Nov 1997, Adam McDougall wrote:

> Has this new kind of nuke been addressed, and can it be/has it been
> fixed?  I just cvsupped sunday, is mine fixed? thanks.


  Perhaps you explain what the hell "teardrop" is, and why we should care.

Tom