Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!netnews.nwnet.net!selway.umt.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.bugs Subject: Re: FreeBSD, fd0d: hard error Date: 9 Sep 1994 17:41:30 GMT Organization: Montana State University, Bozeman Montana Lines: 26 Message-ID: <34q6oa$nhl@pdq.coe.montana.edu> References: <33j9hp$41l@sol.sun.csd.unb.ca> <34a91e$h2f@sol.sun.csd.unb.ca> <34iv96$ik4@pdq.coe.montana.edu> <34lk6g$d44@orion.cc.andrews.edu> NNTP-Posting-Host: 153.90.192.29 In article <34lk6g$d44@orion.cc.andrews.edu>, Andrew Gillham <gillham@andrews.edu> wrote: >>I find that to get the install floppies to work ALL the time, I have to >>reformat under DOS every time I re-write them. Again, this could be >>a picky driver, but it seems to do the trick. >I'm being cynical when I say: >"Why should I have to boot f**kin' DOS to use a floppy under BSD?" :-) Agreed. But, I was sharing my experiences, not agreeing that it should be that way. >I know, I can write the f**kin' fd.c myself!!! Seriously though, it >seems like something broke recently. (or a while ago and I just noticed >it!) I'll try the "format it under DOS to get it to work" trick... The kernel changed significantly in 1.1.5, so it's possible that the timing did change. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.