From owner-freebsd-bugs  Fri Oct 29 23:47:47 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0CA6914F66; Fri, 29 Oct 1999 23:47:45 -0700 (PDT)
	(envelope-from phk@FreeBSD.org)
Received: (from phk@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id XAA50812;
	Fri, 29 Oct 1999 23:47:44 -0700 (PDT)
	(envelope-from phk@FreeBSD.org)
Date: Fri, 29 Oct 1999 23:47:44 -0700 (PDT)
From: <phk@FreeBSD.org>
Message-Id: <199910300647.XAA50812@freefall.freebsd.org>
To: miek@q8.se, phk@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: kern/14590: kernel panic writing to floppy
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: kernel panic writing to floppy

State-Changed-From-To: open->suspended
State-Changed-By: phk
State-Changed-When: Fri Oct 29 23:46:18 PDT 1999
State-Changed-Why: 
This is no longer a problem for since block devices now act as char devices.
I am not sure however, if this problem would also manifest itself if the
faulty floppy was mounted as a filesystem, therefore the "suspend" state.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message