From owner-freebsd-bugs Tue Jun 13 22:35:41 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA09794 for bugs-outgoing; Tue, 13 Jun 1995 22:35:41 -0700 Received: from pelican.com (pelican.com [134.24.4.62]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id WAA09773 for ; Tue, 13 Jun 1995 22:35:30 -0700 Received: by pelican.com (Smail3.1.28.1 #5) id m0sLl6j-000K0pC; Tue, 13 Jun 95 22:35 WET DST Message-Id: From: pete@pelican.com (Pete Carah) Subject: msdos floppy problem To: bugs@freebsd.org Date: Tue, 13 Jun 1995 22:35:17 -0700 (PDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 796 Sender: bugs-owner@freebsd.org Precedence: bulk System: Current from about 2-3 weeks ago; I don't think anything has changed in msdosfs... With a miscellaneous dos floppy (1.44mb 3.5") that I needed to get data from, "mount -t msdos /dev/fd0.1440 /a" then "ls -l /a" gave a half-screen of garbage followed by a decent directory (there were only 2 files in the disks root; one a .exe and the other a directory, which contained 2 regular files). At least this garbage didn't scramble cons25 :-) mdir/mcopy saw it just fine with no bogus entries. (the reason I used mount in the first place was that I didn't yet have mtools; I ended up downloading it in midstream, in disgust.) Don't know what the problem is unless the directory read isn't getting truncated at the first 0 leading byte (or is that still a valid dos optimization?) -- Pete