Installation instructions for Firefox somewhere?

John lists at
Mon Feb 28 22:49:18 GMT 2005

On Mon, 28 Feb 2005 22:35:54 +0100, Anthony Atkielski wrote
> Chris Hodgins writes:
> > Sounds like the perfect time for them to go wrong.  They have been doing
> > the same thing for 8 years without problem.
> They are still doing the same thing today.  There is no additional
> stress in changing operating systems.
> > Suddenly you come along and give them a good old shake up...I would
> > imagine this would be the perfect occasion for this to happen.
> I have no idea what you mean by this.  No "shake-up" is involved.  They
> do the same I/O they've always been doing.  They have no idea whether
> it's Windows NT starting the I/O or FreeBSD.  It all looks the same 
> to the drives.

Have you considered the possibility that windows just didn't report the error?
Just because it is unreported under windows doesn't mean it's not happening...

And just because it has been working for 8 years without a problem doesn't
mean it will go working for a further 8, even if you change nothing..

Saying that, I do notice that sometimes, I do get scsi errors on boot, but
then again I have modified the delay in probing the devices from 15000ms to
5000 in order to speed up boot. Probably unwise, given that the system has 2
scsi cards in, and as well as 5 drives, a scsi cdrom, it also has a scanner,
which is slow to wake up.

Saying *that*, on boot, one card always boots up fast. Sometimes the other
card also boots up, sometimes it times out. But at the login prompt,
everything on the system is up. This is prior to the boot loader loading, so
it cannot possibly be FreeBSD.

You haven't told us what you mean by scsi errors. Is it like I describe, or is
it subsequent to bootup?
lists at

More information about the freebsd-questions mailing list