On Mon, 29 Jan 2001, Bruce McCulley wrote:
> That's the kind of thing that makes me wonder if the real culprit is h/w.
With NT, who can tell? The system's been running fine since we hooked it up
the LAN, so there is nothing to trouble-shoot.
> I started wondering about that when I attended a Red Hat seminar where
> some attendees asked whether they'd fixed "stability" problems in certain
> areas, and other audience members reported using the same s/w features in
> similar fashion without encountering problems.
That could be hardware. But it could just as likely be:
- User error on the part of the people having trouble
- A legitimate bug that only triggers in their particular configuration
Without more information, it is impossible to know.
> Ben's comment about how that system's been "fine" since being hooked up to
> the LAN might suggest that there's a glitch nesting in the NIC or
> something similar, rather than a s/w bug.
Could be. I think it more likely that there is a bug in the NIC driver or
NT's network routines, where the code was written with the assumption that it
would never be disconnected for that long.
This, incidentally, is what I consider to be one of the key advantages of
Linux. NT pretty much has one error message: Blue Screen of Death. At least
Linux gives you *useful* diagnostics when it fails.
--
Ben Scott <[EMAIL PROTECTED]>
Net Technologies, Inc. <http://www.ntisys.com>
Voice: (800)905-3049 x18 Fax: (978)499-7839
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
