Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!decwrl!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!uunet!pitt.edu!mopar From: mopar+@pitt.edu (Jerome A Marella) Newsgroups: comp.os.386bsd.questions Subject: Re: FreeBSD with MFM disks? Message-ID: <13730@blue.cis.pitt.edu> Date: 3 Feb 94 03:34:05 GMT References: <wilko.759747597@spoetnix.idca.tds.philips.nl> <13328@blue.cis.pitt.edu> <2if70c$pv8@pdq.coe.montana.edu> Sender: news+@pitt.edu Organization: University of Pittsburgh Lines: 28 In article <2if70c$pv8@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >>I had to rewrite the fs disk after every time it failed. If I didn't it would >>not mount the floppy the next time I tried to use it. > >That sounds like hardware problems, especially considering the below. > >>I noticed that a lot of the time the fs floppy was mounted read-only for some >>reason. I used both 5 1/4" and 3 1/2" disks and I know how to tell if they are >>write enabled. > >If you don't need to write to the disk, why mount it read/write for safety >reasons? Also, how could the disks get corrupted if they were read-only? I think the installation program does write something to the filesystem floppy. Why do the install notes say that you must not write protect the filesystem floppy? I'll try it write protected and see what happens. Maybe there is somekind of strange hardware problem, but I used the netbsd install disk to get the hard drive set up to boot etc. installed the base Freebsd dist. and am now using the Freebsd 1.0.2 generic kernel with no problems. I just don't understand why the Freebsd install disks didn't work. Jerome -- -- Jerome A. Marella Computing and Information Services, University of Pittsburgh mopar+@pitt.edu