From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 12:49:49 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 A17A016A4CE for ; Tue, 22 Mar 2005 12:49:49 +0000 (GMT) Received: from trans-warp.net (hyperion.trans-warp.net [216.37.208.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2DBE43D41 for ; Tue, 22 Mar 2005 12:49:46 +0000 (GMT) (envelope-from bsilver@chrononomicon.com) Received: from [127.0.0.1] (unverified [65.193.73.208]) by trans-warp.net (SurgeMail 2.2g3) with ESMTP id 722517 for ; Tue, 22 Mar 2005 07:49:47 -0500 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <1975192207.20050322041925@wanadoo.fr> References: <423E116D.50805@usmstudent.com> <423EEE60.2050205@dial.pipex.com> <18510151385.20050321193911@wanadoo.fr> <1975192207.20050322041925@wanadoo.fr> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <376090f278a660716d7b251f720d93d4@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Tue, 22 Mar 2005 07:49:44 -0500 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.619.2) X-Server: High Performance Mail Server - http://surgemail.com X-Authenticated-User: bsilver@chrononomicon.com X-DNS-Paranoid: DNS ptr lookup of (65.193.73.208) failed 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, 22 Mar 2005 12:49:49 -0000 On Mar 21, 2005, at 10:19 PM, Anthony Atkielski wrote: > Freminlins writes: > >> Alternatively, show us it is not a firmware problem first. > > It ran for eight years without errors. > >> It's not throwing darts, it's sensible advice. NT is ancient, like >> your firmware no doubt. > > So your saying an anciety copy of NT is more reliable than a current > copy of FreeBSD? Holy Hannah would you just update the damn firmware as even the VENDOR would recommend and then move on from there instead of baiting people? Every damned vendor I've worked with likes recommending a firmware update after the obvious "are the cables connected" question is posed. Even for a !@#$ printer we had problems using with NetWare...and the firmware update DID fix it!