From owner-freebsd-current  Tue Sep  3 09:52:39 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id JAA11006
          for current-outgoing; Tue, 3 Sep 1996 09:52:39 -0700 (PDT)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA11001
          for <current@freebsd.org>; Tue, 3 Sep 1996 09:52:36 -0700 (PDT)
Received: from rover.village.org (localhost [127.0.0.1]) by rover.village.org (8.7.5/8.6.6) with ESMTP id KAA27084; Tue, 3 Sep 1996 10:52:19 -0600 (MDT)
Message-Id: <199609031652.KAA27084@rover.village.org>
To: Paul DuBois <dubois@primate.wisc.edu>
Subject: Re: Food for thought 
Cc: current@freebsd.org
In-reply-to: Your message of Tue, 03 Sep 1996 11:50:09 CDT
Date: Tue, 03 Sep 1996 10:52:19 -0600
From: Warner Losh <imp@village.org>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

: Does -current handle these situations better?

I've seen reports of problems with 2.1 and some versions of stable
(like until early spring).  My -current box from July onward has been
happy as a clam with the Jaz drive, even with sleep mode.

I've not tried 2.1.5R, but I have reason to believe that it works
there as well.

Warner