From owner-freebsd-stable  Fri Nov  8 16:51:13 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA23498
          for stable-outgoing; Fri, 8 Nov 1996 16:51:13 -0800 (PST)
Received: from tahoma.cwu.edu (skynyrd@tahoma.cwu.edu [198.104.65.220])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id QAA23492
          for <stable@FreeBSD.ORG>; Fri, 8 Nov 1996 16:51:08 -0800 (PST)
Received: by tahoma.cwu.edu; id AA02134; Fri, 8 Nov 1996 16:51:01 -0800
Date: Fri, 8 Nov 1996 16:51:01 -0800 (PST)
From: Chris Timmons <skynyrd@tahoma.cwu.edu>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: stable@FreeBSD.ORG
Subject: FDDI DRIVER: The curtain is going down on 2.1-stable in 5 days!
In-Reply-To: <10472.847447745@time.cdrom.com>
Message-Id: <Pine.OSF.3.95.961108164419.31236B-100000@tahoma.cwu.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


Matt Thomas mentioned sending updated FDDI code last summer which has at
least one fix for fast CPUs.  Additionally the 'unknown packet type'
messages which have become a FAQ are zapped in the updated code. 

Considering the relatively small amount of work to integrate and the
highly reliable source of the code, do you think it could be committed
prior to 2.1.6? 

Regards,
-Chris


On Fri, 8 Nov 1996, Jordan K. Hubbard wrote:

> Basically, I need to get 2.1.6 off my plate if I'm to have any hope of
> working constructively on 2.2, and managing 3 different branches
> during this transitional period is also something of a headache which
> I'd like to avoid prolonging.
> 
> So.  David and I have decided that next Tuesday, the 12th of November,
> would be an excellent time to start putting FreeBSD 2.1.6 to bed, and
> if you've got any critical bug fixes or security problems to report in
> 2.1-stable, now would be an excellent time to raise them before it's
> too late.