Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!news-feed-2.peachnet.edu!concert!rutgers!twwells!bill From: bill@twwells.com (T. William Wells) Newsgroups: comp.os.386bsd.questions Subject: Re: odd hard disk error installing netbsd-0.8 Message-ID: <CBo6r3.DCB@twwells.com> Date: 12 Aug 93 23:33:01 GMT References: <CBMG17.Ir@twwells.com> <1993Aug12.073325.13417@monu6.cc.monash.edu.au> Organization: None, Mt. Laurel, NJ Lines: 17 In article <1993Aug12.073325.13417@monu6.cc.monash.edu.au> ins413j@mdw059.cc.monash.edu.au (Markfried Fellensiek) writes: : T. William Wells (bill@twwells.com) wrote: : : I'm running a system with a wd1007 esdi controller and a micropolis 1355 disk. : : : : at this instant. (I have two identical disks, which I physically swap. One for : : my running system and one for play.) : : I'm sure you don't UNPLUG one drive to use the other, then PLUG the other : one back in again? (THERE IS a software alternative!? (I'm sure 2 :) )) Actually, that is exactly what I do. No software alternative will work when one is switching between two distinct operating systems and where one of them might very well decide to overwrite critical data on the other disk. True, I could probably cobble a write protect switch for the drive but then I'm left with the problem that neither of the two operating systems can be coerced with any reasonable amount of effort to boot off a second esdi drive.