From owner-freebsd-questions@FreeBSD.ORG Tue Mar 29 14:03:14 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 97A1416A4CE for ; Tue, 29 Mar 2005 14:03:14 +0000 (GMT) Received: from makeworld.com (makeworld.com [216.201.118.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 364DF43D1D for ; Tue, 29 Mar 2005 14:03:14 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id 8CE3B60E4 for ; Tue, 29 Mar 2005 08:03:13 -0600 (CST) Received: from makeworld.com ([127.0.0.1]) by localhost (makeworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17188-10 for ; Tue, 29 Mar 2005 08:03:11 -0600 (CST) Received: from [216.201.118.138] (racerx.makeworld.com [216.201.118.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by makeworld.com (Postfix) with ESMTP id 49FC460D6 for ; Tue, 29 Mar 2005 08:03:10 -0600 (CST) Message-ID: <42496060.1060404@makeworld.com> Date: Tue, 29 Mar 2005 08:04:16 -0600 From: Chris User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050327) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <42480F8B.1060405@makeworld.com> <1648629793.20050329122346@wanadoo.fr> In-Reply-To: <1648629793.20050329122346@wanadoo.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by ClamAV 0.75.1/amavisd-new-2.2.1 (20041222) at makeworld.com - Isn't it ironic Subject: Re: Anthony's drive issues.Re: ssh password delay X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: racerx@makeworld.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Mar 2005 14:03:14 -0000 Anthony Atkielski wrote: > Ted Mittelstaedt writes: > > >>The main point I've been trying to make is that just because FreeBSD's >>drivers don't support whatever modification has been made in the Adaptec >>code on the Vectra, does not mean that the FreeBSD driver is "broken" >>or "has a bug" in it. > > > When something doesn't work, it's broken. I disagree - If FBSD does not (or did not) know of the HP/Compaq tweakes in the microcode, how can you claim it's broken? If MS does not support or have a driver for so-and-so app or hardware, does it also mean Windows is broken? According to you, it is. According to the vast majority, it's not broken, it's merely unsupported. You could say the same about your hardware based on what you just said, if FBSD does not have the teaks to the driver version you need, then (as you think) your hardware is broken. As you stated, you can't have it both ways. Why not just agree that both FBSD AND your hardware are broken? Oh - I know, it worked for 8 years... Read above to if MS don't support or have a driver for x, y, and z - then as you say, Windows is broken. Can't have it both ways mate. Know the difference. -- Best regards, Chris The time it takes to rectify a situation is inversely proportional to the time it took to do the damage.