From owner-freebsd-questions@FreeBSD.ORG Tue Mar 29 16:34:50 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E51AF16A4CE for ; Tue, 29 Mar 2005 16:34:50 +0000 (GMT) Received: from mta05-winn.mailhost.ntl.com (smtpout15.mailhost.ntl.com [212.250.162.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E933643D41 for ; Tue, 29 Mar 2005 16:34:49 +0000 (GMT) (envelope-from scott@fishballoon.org) Received: from aamta04-winn.mailhost.ntl.com ([212.250.162.8]) by mta05-winn.mailhost.ntl.com with ESMTP <20050329163448.GIAW12099.mta05-winn.mailhost.ntl.com@aamta04-winn.mailhost.ntl.com>; Tue, 29 Mar 2005 17:34:48 +0100 Received: from llama.fishballoon.org ([81.104.196.104]) by aamta04-winn.mailhost.ntl.com with ESMTP <20050329163448.RVCI1352.aamta04-winn.mailhost.ntl.com@llama.fishballoon.org>; Tue, 29 Mar 2005 17:34:48 +0100 Received: from scott by llama.fishballoon.org with local (Exim 4.50 (FreeBSD)) id 1DGJfy-000Oo3-JQ; Tue, 29 Mar 2005 17:34:46 +0100 Date: Tue, 29 Mar 2005 17:34:46 +0100 From: Scott Mitchell To: Anthony Atkielski Message-ID: <20050329163445.GA93429@llama.fishballoon.org> References: <42480F8B.1060405@makeworld.com> <20050329125024.4d3577d3.dick@nagual.st> <396996207.20050329132534@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <396996207.20050329132534@wanadoo.fr> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.11-RELEASE i386 Sender: Scott Mitchell cc: freebsd-questions@freebsd.org Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 16:34:51 -0000 On Tue, Mar 29, 2005 at 01:25:34PM +0200, Anthony Atkielski wrote: > > My point was that FreeBSD doesn't work on the machine. I wanted to know > why. I still don't know why it doesn't work on the machine. Apparently > nobody here really knows how FreeBSD works. So you keep saying. It probably is true that the people who maintain whichever Adaptec driver it was you're having trouble with - who I guess would 'really know how FreeBSD works' in this context - don't follow the -questions list too closely. Really, your best bet at this point is to gather up all the error messages, boot-time output, details of the BIOS/microcode versions of your adapter, etc. and file a PR. You clearly have identified a real problem, and that is the officially supported way of getting it looked at. Regards, Scott