Date: Tue, 22 Mar 2005 07:49:44 -0500 From: Bart Silverstrim <bsilver@chrononomicon.com> To: freebsd-questions@freebsd.org Subject: Re: Anthony's drive issues.Re: ssh password delay Message-ID: <376090f278a660716d7b251f720d93d4@chrononomicon.com> In-Reply-To: <1975192207.20050322041925@wanadoo.fr> References: <423E116D.50805@usmstudent.com> <423EEE60.2050205@dial.pipex.com> <18510151385.20050321193911@wanadoo.fr> <eeef1a4c0503211224572d64e4@mail.gmail.com> <1975192207.20050322041925@wanadoo.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
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!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?376090f278a660716d7b251f720d93d4>