From owner-freebsd-questions@FreeBSD.ORG Mon Mar 21 18:45:52 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 9A22816A4CE for ; Mon, 21 Mar 2005 18:45:52 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B9643D5C for ; Mon, 21 Mar 2005 18:45:52 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 4B9AC1C00099 for ; Mon, 21 Mar 2005 19:45:51 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1108.wanadoo.fr (SMTP Server) with ESMTP id 1EF7B1C0008A for ; Mon, 21 Mar 2005 19:45:51 +0100 (CET) X-ME-UUID: 20050321184551126.1EF7B1C0008A@mwinf1108.wanadoo.fr Date: Mon, 21 Mar 2005 19:45:50 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <686409441.20050321194550@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: References: <5810323424.20050321052023@wanadoo.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: MS Exchange server on FreeBSD? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Mar 2005 18:45:52 -0000 Ted Mittelstaedt writes: > The problem is you just don't want it to be a hardware problem because > you don't accept the possibility that the NT driver wrote around a > hardware problem and the FreeBSD driver doesen't. No, I don't want to run on a wild goose chase just because it hurts someone's pride to think that FreeBSD might have a bug. The only thing that changed on this machine was a move from Windows NT to FreeBSD. Therefore the source of the problem is FreeBSD. > Despite the fact that making up for hardware problems with > writearounds in the software drivers is a common thing in the > industry. That would explain the "quirks" coding in FreeBSD, then, wouldn't it? Or is this only bad when other operating systems do it? > So you won't do the testing to prove that it is or isn't a hardware > bug, and thus you can continue pretending to yourself that it must be > software, and thus not your responsibility. Nobody here knows enough about FreeBSD to even tell me what its messages mean; I don't see any particular reason to knock myself out indulging their baseless conjectures. -- Anthony