From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 13:34:59 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 EBE4816A4CE for ; Tue, 22 Mar 2005 13:34:58 +0000 (GMT) Received: from trans-warp.net (hyperion.trans-warp.net [216.37.208.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B68543D1F for ; Tue, 22 Mar 2005 13:34:58 +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 727636 for ; Tue, 22 Mar 2005 08:35:01 -0500 Mime-Version: 1.0 (Apple Message framework v619.2) In-Reply-To: <1404322406.20050322112613@wanadoo.fr> References: <423E116D.50805@usmstudent.com> <423EEE60.2050205@dial.pipex.com> <18510151385.20050321193911@wanadoo.fr> <1975192207.20050322041925@wanadoo.fr> <1688160068.20050322102514@wanadoo.fr> <1404322406.20050322112613@wanadoo.fr> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Tue, 22 Mar 2005 08:34:51 -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 13:34:59 -0000 On Mar 22, 2005, at 5:26 AM, Anthony Atkielski wrote: > Freminlins writes: > >> So stick with NT. Why would you change from something that runs >> perfectly for 8 years? > > I was able to retire the legacy applications on the machine and I > wanted > to try something new. And you ran into a snag that you can't work through. Most people if they were doing this on a lark would either replace the hardware or try a different distro. There's some hardware here that I've gone through probably three or four different liveboot CDs of Linux to get working properly just because I didn't want to dedicate the time to troubleshooting every last config problem. Although when it comes to SCSI bus resets, it seemed to usually be a problem with one of the drives or the controller going bad. When I ran into that error before, I remember seeing another person post to a list saying that NT doesn't report the reset error. Linux did. Maybe this is what you're running into? >> That doesn't mean nothing has changed in 20 years, does it? > > It means that the age of the OS is not an issue. But...didn't you bring that up? And the design of the OS may be 20 years old, but the OS most people are using isn't. >> And your hardware seems to not work very well with FreeBSD. Move on. > > No, FreeBSD doesn't work very well with the hardware. As a matter of > fact, it doesn't work very well with the hardware on my production > server, either. Is the hardware on the compatibility list? What is it? > It seems that as soon as you install FreeBSD on a machine, the > "hardware" fails. If this is your gripe, then go back or work with people (without baiting them) to get it looked at. If your production server isn't unsupported hardware, people may try to help you. If this isn't what you want to pursue as an avenue, then install something else. My impression is that you installed it, it had some errors, and after people said they've had this happen with bad hardware, you simply refuse to believe the possibility that something could have been wrong but NT didn't *TELL* you about it, and then want to launch into an attack on the OS in a list where people are running FreeBSD quite happily on a wide range of hardware. The stories just don't jive. You're implying it doesn't work and is crap because all your hardware isn't working with it. This list is populated by people that have worked out problems and configuration errors and are running it without trouble. Something just intuitively tells me that at this point you're more concerned with pissing people off to make a point. Most people trying this on a lark would say, well, it didn't work, so maybe I'll try this instead...if it's not worth your time to try fixing it. You implied you did this installation on a lark. Well, let it go then. Try a Linux distro. I've seen posts by people before saying they use Linux Live CD's to test laptops at stores before buying. Probably the best thing for you to try is Linux Knoppix on your server, see if it boots and sees errors. If Linux *and* FBSD see errors, I think it's safe to say it is a problem with your hardware that NT wasn't reporting. Especially if your hardware is on the compatibility list and is erroring out. >> That's not what has been said. Having read this thread (and others by >> you previously) you have no intention of helping yourself. > > What would you suggest that I do? It takes a very long time to wade > through OS source code. Read my above suggestions.