From owner-freebsd-alpha Wed Jun 7 1:14:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from eel.radicalmedia.com (eel.radicalmedia.com [204.254.246.9]) by hub.freebsd.org (Postfix) with ESMTP id 96CF137B7AF for ; Wed, 7 Jun 2000 01:14:15 -0700 (PDT) (envelope-from phiber@eel.radicalmedia.com) Received: (from phiber@localhost) by eel.radicalmedia.com (8.9.3/8.9.3) id EAA04980 for freebsd-alpha@freebsd.org; Wed, 7 Jun 2000 04:14:13 -0400 (EDT) Date: Wed, 7 Jun 2000 04:14:13 -0400 From: Mark Abene To: freebsd-alpha@freebsd.org Subject: msdosfs is broken... Message-ID: <20000607041413.B4164@radicalmedia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Regarding my earlier message regarding msdos images and the vn driver, it turns out that there's nothing wrong with the vn driver at all. It's the msdosfs driver that appears broken. I just tried mounting an actual msdos floppy, and trying to read or write files greater than 1024 bytes returns "Argument list too long" and fails. I'm running 4.0-RELEASE. Can anyone else verify this problem? I've filed it as PR misc/19086 with gnats. MSDOSFS support is compiled into the kernel. Mounting and unmounting the floppy causes no errors. Thanks, -Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message