From owner-freebsd-questions@FreeBSD.ORG Mon Feb 28 12:22:38 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 EC04816A4CE for ; Mon, 28 Feb 2005 12:22:38 +0000 (GMT) Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [65.75.192.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9752043D53 for ; Mon, 28 Feb 2005 12:22:38 +0000 (GMT) (envelope-from tedm@toybox.placo.com) Received: from tedwin2k (nat-rtr.freebsd-corp-net-guide.com [65.75.197.130]) j1SCMdb16142; Mon, 28 Feb 2005 04:22:39 -0800 (PST) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Ramiro Aceves" , Date: Mon, 28 Feb 2005 04:22:37 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <42224A80.9010109@wanadoo.es> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: Normal Subject: RE: Installation instructions for Firefox somewhere? 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, 28 Feb 2005 12:22:39 -0000 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Ramiro Aceves > Sent: Sunday, February 27, 2005 2:33 PM > To: freebsd-questions@freebsd.org > Subject: Re: Installation instructions for Firefox somewhere? > > > Anthony, I understand your frustration. I think you should fix > the SCSI > problems before doing anything. The ports collection really works very > well. Perhaps some experts here can help you with your SCSI. I am a > FreeBSD novice ;-) > I agree Ramiro, I've setup dozens and dozens of different SCSI setups, and I think that his problem is hardware, such as incorrect termination, a bad scsi cable, bad connectors on the cable, or an incompatible SCSI/disk combination (which is rare, but it does happen) Others have suggested this to him though and he either ignores them or insists he's checked all that. Ted