From owner-freebsd-hackers  Sun Dec 18 14:43:31 1994
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id OAA03638 for hackers-outgoing; Sun, 18 Dec 1994 14:43:31 -0800
Received: from time.cdrom.com (time.cdrom.com [192.216.223.46]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id OAA03559; Sun, 18 Dec 1994 14:43:20 -0800
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.9/8.6.9) with SMTP id OAA18713; Sun, 18 Dec 1994 14:43:37 GMT
X-Authentication-Warning: time.cdrom.com: Host localhost didn't use HELO protocol
To: Nate Williams <nate@bsd.coe.montana.edu>
cc: hackers@freebsd.org, current@freebsd.org
Subject: Re: Don't scream.. 
In-reply-to: Your message of "Sun, 18 Dec 94 12:52:52 MST."
             <199412181952.MAA12590@bsd.coe.montana.edu> 
Date: Sun, 18 Dec 1994 14:43:36 +0000
Message-ID: <18712.787761816@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

Does this still occur when you roll-back Garrett's changes?
This is our likely course of action for 2.0.5.

					Jordan

> > I've talked to both Poul-Henning Kamp and David Greenman about this,
> > and we all think that a snap-shot of FreeBSD-current under the
> > brand-name (and version) of 2.0.5 is quite possible, and perhaps even
> > eminently desirable.  Sure, there will be some bugs in -current.
> 
> It appears there are some pretty significant bugs in the networking code
> that need to be addressed before -current would be usable.  Most of the
> people running -current report that they can't get their IP connections
> to work at all, and this is completely unacceptable for a BSD OS.
> 
> To me, the above bug is much worse than throwing together another
> release that is not well-tested.
> 
> 
> 
> Nate