[Fwd: current Redhat user evaluates Debian]
.
debs,
..so, when this happens, what can be done? (i think i tried some
sort of *probe and that was last time i "saw" my printing (lpr)
and dialout (pon) capabilities.)
regretting a possible reinstall on a potato box that was
perfect,
bentley taylor.
//
John Hasler wrote:
Some drivers "probe" for their hardware by attempting to access
various
ports. In a few pathological cases, the probing by one driver
will put
hardware belonging to another into a state that crashes or locks
up the
system. This is one of the major headaches of automatic hardware
detection.
--
--- Begin Message ---
- To: debian-user@lists.debian.org
- Subject: Re: current Redhat user evaluates Debian
- From: John Hasler <john@dhh.gt.org>
- Date: 30 Jul 2000 19:36:53 -0500
- Message-id: <87g0orf84a.fsf@toncho.dhh.gt.org>
- In-reply-to: Olaf Meeuwissen's message of "31 Jul 2000 08:59:00 +0900"
- References: <20000728111816.A28000@fjellstad.org> <Pine.GSO.4.21.0007281421010.5424-100000@www.storm.ca> <20000729171655.C2564@fjellstad.org> <87n1izqiez.fsf@epkowa.co.jp>
Olaf Meeuwissen writes:
> Don't know about damaging or messing anything up, but certain modules may
> have to loaded during the boot.
Some drivers "probe" for their hardware by attempting to access various
ports. In a few pathological cases, the probing by one driver will put
hardware belonging to another into a state that crashes or locks up the
system. This is one of the major headaches of automatic hardware
detection.
--
John Hasler
john@dhh.gt.org
Dancing Horse Hill
Elmwood, Wisconsin
--
Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
--- End Message ---
Reply to: