From owner-freebsd-bugs  Tue Dec 19 07:36:50 1995
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA16912
          for bugs-outgoing; Tue, 19 Dec 1995 07:36:50 -0800 (PST)
Received: from pain.csrv.uidaho.edu (root@pain.csrv.uidaho.edu [129.101.114.109])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA16884
          for <freebsd-bugs@freebsd.org>; Tue, 19 Dec 1995 07:36:42 -0800 (PST)
Received: from pain.csrv.uidaho.edu (fn@localhost [127.0.0.1]) by pain.csrv.uidaho.edu (8.6.12/8.6.9) with ESMTP id HAA00488; Tue, 19 Dec 1995 07:35:30 -0800
Message-Id: <199512191535.HAA00488@pain.csrv.uidaho.edu>
To: Martin Sapsed <m.sapsed@bangor.ac.uk>
cc: freebsd-bugs@freebsd.org
Subject: Re: Problem with FreeBSD 2.1.0-RELEASE 
In-reply-to: Your message of "Tue, 19 Dec 1995 12:56:37 GMT."
             <Pine.OSF.3.90.951219125220.3779C-100000@thunder> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <481.819387329.1@pain.csrv.uidaho.edu>
Date: Tue, 19 Dec 1995 07:35:29 -0800
From: Faried Nawaz <fn@pain.csrv.uidaho.edu>
Sender: owner-bugs@freebsd.org
Precedence: bulk

Martin Sapsed wrote...

   I must point out I'm no kernel hacker so am rather in the dark here. I 
   currently have another machine running FreeBSD 1.0 which (mostly) happily 
   accesses 11 drives so this bug seems to have been introduced sometime 
   since then?

1.0?!?  gimme!  :)

faried, 1.0 -> 1.1-g -> 1.1.5.1 -> 2.0 -> 2.0.5 -> current