Date: Wed, 7 Jun 2000 22:02:43 -0400 From: Mark Abene <phiber@radicalmedia.com> To: freebsd-alpha@FreeBSD.ORG Cc: paulp@uts.amdahl.com Subject: Re: msdosfs is broken... Message-ID: <20000607220243.B13423@radicalmedia.com> In-Reply-To: <20000607041413.B4164@radicalmedia.com>; from Mark Abene on Wed, Jun 07, 2000 at 04:14:13AM -0400 References: <20000607041413.B4164@radicalmedia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I've been poking around in /sys/msdosfs and come to the conclusion that much of the use of u_long's and long's are causing the breakage on the alpha. I'm copying this message to the author of the code, but was just curious if anyone on this list is responsible for the code where it concerns portability issues on the alpha? Cheers, -Mark On Wed, Jun 07, 2000 at 04:14:13AM -0400, Mark Abene wrote: > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000607220243.B13423>