From owner-freebsd-questions@FreeBSD.ORG Tue Mar 22 15:49:27 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 775B016A50C for ; Tue, 22 Mar 2005 15:49:27 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80B5243D48 for ; Tue, 22 Mar 2005 15:49:26 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id BC7561C000B1 for ; Tue, 22 Mar 2005 16:49:25 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1106.wanadoo.fr (SMTP Server) with ESMTP id 84AE11C0008A for ; Tue, 22 Mar 2005 16:49:25 +0100 (CET) X-ME-UUID: 20050322154925543.84AE11C0008A@mwinf1106.wanadoo.fr Date: Tue, 22 Mar 2005 16:49:24 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <802735952.20050322164924@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Anthony's drive issues.Re: ssh password delay 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: Tue, 22 Mar 2005 15:49:27 -0000 Bart Silverstrim writes: > And you ran into a snag that you can't work through. Yes, at least not with the time I have available. > Most people if they were doing this on a lark would either replace the > hardware or try a different distro. There's only one "distro" of FreeBSD. Replacing the hardware defeats the purpose of making good use of existing hardware that still runs perfectly. > 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? Well, if NT didn't report the error, and I never lost the data, how do I get FreeBSD to stop reporting the error? It's more complex than that, though, since FreeBSD also stalls sometimes when these events occur, and sometimes there's a panic. > But...didn't you bring that up? Not that I remember. I feel no compulsion to constantly upgrade hardware and software. > And the design of the OS may be 20 years old, but the OS most people > are using isn't. So? > Is the hardware on the compatibility list? What is it? An AIC7880 SCSI controller. > 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 ... Anything can happen with bad hardware. That doesn't mean that every error you see is bad hardware. When the processor failed on my old server, I got segment violations in all sorts of programs. Does this mean that if I get a segment violation on the new server, I should replace all the hardware--since I've seen segment violations before when a a processor fails? > ... 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. If no data corruption occurred, there was nothing wrong. If NT doesn't have to tell me about it, neither does FreeBSD. But nobody actually knows what is wrong. Nobody has any clue. That's the problem. Lots of people are willing to wildly speculate on this or that hardware problem in order to create the impression that they know what they are talking about, but careful scrutiny of what they say reveals that they are totally ignorant of the real problem. They have no idea but cannot bring themselves to say so. And their idea of troubleshooting is to replace hardware forever because they don't know what the software is doing. > 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. On the same hardware? > Something just intuitively tells me that at this point you're more > concerned with pissing people off to make a point. No, although I do get tired of talking to people who sound like they're still in grade school. I'm accustomed to working with professionals, and professionals address the problem, they don't shoot the messenger. > Probably the best thing for you to try is Linux Knoppix on your server, > see if it boots and sees errors. I suppose I may be forced to try something else; it doesn't look like I'm ever going to get any help with FreeBSD. The problem is, most open-source communities are populated by the same sort of adolescent mentalities; all they want to do is defend their beloved favorite hardware and software and attack anyone who disagrees with them. It's all one big weekend hobby to them, or one sacred religion, or both--but it's certainly not professional IT. That's why open-source is never likely to replace proprietary software ... nobody in the open-source community is willing to grow up. -- Anthony