From owner-freebsd-questions@FreeBSD.ORG Mon Mar 21 19:36:46 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 0F29516A4CE for ; Mon, 21 Mar 2005 19:36:46 +0000 (GMT) Received: from makeworld.com (makeworld.com [216.201.118.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15A5B43D53 for ; Mon, 21 Mar 2005 19:36:45 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id E119F60F3 for ; Mon, 21 Mar 2005 13:36:40 -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 84729-03 for ; Mon, 21 Mar 2005 13:36:37 -0600 (CST) Received: by makeworld.com (Postfix, from userid 1001) id 9359E60E7; Mon, 21 Mar 2005 13:36:37 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id 8049060E4 for ; Mon, 21 Mar 2005 13:36:37 -0600 (CST) Date: Mon, 21 Mar 2005 13:36:37 -0600 (CST) From: RacerX To: freebsd-questions@freebsd.org In-Reply-To: <686409441.20050321194550@wanadoo.fr> Message-ID: <20050321133424.B84708@makeworld.com> References: <5810323424.20050321052023@wanadoo.fr> <686409441.20050321194550@wanadoo.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by ClamAV 0.75.1/amavisd-new-2.2.1 (20041222) at makeworld.com - Isn't it ironic Subject: Re: MS Exchange server on FreeBSD? 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: Mon, 21 Mar 2005 19:36:46 -0000 On Mon, 21 Mar 2005, Anthony Atkielski wrote: > 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 > Oh for fucks sakes, stop insulting the folks that are offering solutions. Like I posted before - upgrade your firmware to meet FBSD half way . How do you expect an OS written for 2005 to play well with shit that was made in 97? Get a grip, stop insulting us - we're NOT the enemy here. However, YOUare makeing them. Best regards, Chris