Date: Thu, 12 Oct 1995 18:16:02 -0700 (MST) From: Terry Lambert <terry@lambert.org> To: scott@statsci.com Cc: gibbs@freefall.freebsd.org, dima@escape.com, questions@freebsd.org, support@freebsd.org Subject: Re: problem Message-ID: <199510130116.SAA16419@phaeton.artisoft.com> In-Reply-To: <m0t3Ve1-000r3xC@main.statsci.com> from "Scott Blachowicz" at Oct 12, 95 02:58:26 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> And in my experience (read: one system), it is broken, period. Are you talking > of _disks_ > ~500Mb or _filesystems_? When I messed with msdosfs on my system > (a 1Gb IDE disk & a 1.4Gb SCSI disk on a 2.0.5R installed from CD) I ended up > getting corrupted BSD partitions for my trouble - even when I only mounted the > msdos slices read-only. And I don't have any slices or filesystems that are > that big. > > The system works great now that I don't get anywhere near the msdos slices. I > CAN just use the mtools package to get at my msdos disks anyways - not as > convenient, but it does seem to work. > > I would LOVE to hear that things have been fixed up in later releases...I > might even try it once I get good backups and a recovery plan thought out... It would help diagnose the problem to make page 0 inaccessable in kernel mode to cause a kernel fault. This would probably fail on pre-486 because of the failure to honor the WP bit in protected mode. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510130116.SAA16419>