From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 27 23:46:43 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0F7A416A415 for ; Wed, 27 Dec 2006 23:46:43 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.freebsd.org (Postfix) with ESMTP id AF7C413C473 for ; Wed, 27 Dec 2006 23:46:41 +0000 (UTC) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id kBRN7JH24991 for ; Thu, 28 Dec 2006 10:07:19 +1100 (EST) Date: Thu, 28 Dec 2006 10:07:18 +1100 (EST) From: Dave Horsfall To: FreeBSD Hackers In-Reply-To: <17810.54292.139339.466850@bhuda.mired.org> Message-ID: References: <45918F6E.90006@digitaldaemon.com> <004c01c7293b$d5e03b40$6500a8c0@laptopt> <4591CB3C.1060902@digitaldaemon.com> <200612261808.08984.mario@schmut.com> <4592690B.7080800@digitaldaemon.com> <17810.54292.139339.466850@bhuda.mired.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: 6.1-RELEASE / 6.2 Kernel Crash... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Dec 2006 23:46:43 -0000 On Wed, 27 Dec 2006, Mike Meyer wrote: > I had an 11/750 that ran BSD 4.2 for years with no problems. When I > tried to upgrade it to BSD 4.3, it would reliably panic in namei during > the boot process. We had about a dozen 750s, and this was our test > machine - so none of them were going to be upgraded until this got > fixed, deadline or no. Heh. We had a PDP-11/40 running Edition 6, and it was unable to use the "overlapped seeks" feature of the RK-11 controller, so of course Unix got blamed by DEC. Turned out that DEC OSs (RSX, RSTS etc) never used that feature, and an FCO was necessary to fix it. -- Dave