From owner-freebsd-hackers Thu Sep 11 17:40:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA12854 for hackers-outgoing; Thu, 11 Sep 1997 17:40:24 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA12839; Thu, 11 Sep 1997 17:40:18 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA17151; Fri, 12 Sep 1997 10:10:14 +0930 (CST) Message-ID: <19970912101014.37786@lemis.com> Date: Fri, 12 Sep 1997 10:10:14 +0930 From: Greg Lehey To: FreeBSD Questions Cc: FreeBSD Hackers Subject: Do *you* have problems with floppies? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I've seen a lot of reports recently about problems with floppies under FreeBSD. Now I can understand a lot of that: floppies must be the most unreliable data storage medium I can think of, not to mention the most expensive per byte. But I'm getting the feeling that there is more to it than that, that possibly there's a bug in the floppy driver and that we're blaming it on the inherent unreliability of the medium. I'm looking for indications which would point towards the driver. One of these might be: 1. Floppy formatted under on the same machine. 2. FreeBSD runs into hardware problems with the floppy (typically things like checksum errors). 3. can read the entire floppy with no trouble. If you can give me hard evidence of such occurrences, I'd like to hear from you. I know that plenty of people can tell me that they've had occurrences of (2), maybe in conjunction with (1), but unless you can prove (3) as well, I don't want to hear from you. In addition, if you have any other evidence I haven't thought of which would also point to an error in the floppy driver, please contact me. Greg