From owner-freebsd-questions Fri Feb 2 7:26: 9 2001 Delivered-To: freebsd-questions@freebsd.org Received: from chmls20.mediaone.net (chmls20.mediaone.net [24.147.1.156]) by hub.freebsd.org (Postfix) with ESMTP id BC32137B4EC for ; Fri, 2 Feb 2001 07:25:51 -0800 (PST) Received: from be-well.ilk.org (lowellg.ne.mediaone.net [24.147.184.128]) by chmls20.mediaone.net (8.11.1/8.11.1) with ESMTP id f12FPo602512; Fri, 2 Feb 2001 10:25:50 -0500 (EST) Received: (from lowell@localhost) by be-well.ilk.org (8.11.2/8.11.2) id f12FPnF03215; Fri, 2 Feb 2001 10:25:50 -0500 (EST) (envelope-from lowell) To: freebsd-questions@freebsd.org, meshko@cs.brandeis.edu Subject: Re: bad floppy causes reset References: From: Lowell Gilbert Date: 02 Feb 2001 10:25:46 -0500 In-Reply-To: meshko@cs.brandeis.edu's message of "31 Jan 2001 20:17:20 +0100" Message-ID: <447l39umx0.fsf@lowellg.ne.mediaone.net> Lines: 11 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG meshko@cs.brandeis.edu (Mikhail Kruk) writes: > is it a known problem that reading a bad floppy can cause 4.2 to reset > (4.2-STABLE)? Or should I send pr? Known problem, very long standing (same problem as trying to write to a read-only disk). I thought it was supposed to get fixed as a side effect of some other work, but my hazy memory may just be wrong. Another PR couldn't hurt, although contacting phk or bde would be another strategy. Check list archives for more information, I guess. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message