Date: Sun, 22 Feb 1998 13:47:29 -0800 (PST) From: Brian Handy <handy@sag.space.lockheed.com> To: hackers@FreeBSD.ORG Cc: Jordan Hubbard <jkh@FreeBSD.ORG> Subject: VFATFS Status Message-ID: <Pine.OSF.3.96.980222132844.8507A-100000@sag.space.lockheed.com>
next in thread | raw e-mail | index | archive | help
Heya folks, We tried the Luoqi patch on ftp.freebsd.org for vfatfs, and the following missive from my test subject is the result. These aren't the same as the ones in -current. Our results are included below. (There is probably something else up with the ZIP drive, but I surmise we should be able to read the Win95 partition. I wasn't present for this experiment so I can't say exactly what transpired.) I know Jordan is looking for results on this, maybe in part as a candidate for -STABLE. If I can find a version of these that apply to -STABLE, I'm willing to give it a try. If I grab the -CURRENT msdosfs, is there any hope I can get it to compile in -STABLE? We can give it a try here... Thanks, Brian ---------- Forwarded message ---------- Date: Sun, 22 Feb 98 12:26:45 -0800 To: Brian Handy <handy@sag.space.lockheed.com> Subject: Re: VFAT? No joy. I made the patch, it didn't complain. I re-made the kernel, no complaints that I noticed and it boots OK (also changed some kernel options, mostly removing a few obvious things like CPU386). But if I try to mount wd0 or wd3 (where I deduce the Zip drive is), I get invalid arg messages except occassionally I get hard read errors on the Zip and the light goes on the drive. Without the -t msdos, it kicks me off with a different error (bad zero block or somesuch, I can jot these down if it would be useful). Mounting floppies with the -t msdos switch does work so I don't think it was just the wine last night. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.96.980222132844.8507A-100000>