Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!nntp.coast.net!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Installation Problem (2 hard disks with Win95 & FreeBSD) Date: 11 Aug 1996 18:01:48 GMT Organization: Private BSD site, Dresden Lines: 31 Message-ID: <4ul76c$nk@uriah.heep.sax.de> References: <4u53gb$6ik@mambo.cs.wustl.edu> <4ug4ep$4l8@uriah.heep.sax.de> <320D85E5.41C67EA6@diac.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Paul Newhouse <pimin@diac.com> wrote: > > that you want a boot manager. This way, it will be placed on both > > disks which is necessary to toggle between them. > > Are you sure you want it on both disks? I had a real problem with that I am sure. That's the only way how it can toggle back and forth between both disks. > BTW - I also found that when I added a third bootable disk that selecting > > wd(2,a)/netbsd > > didn't work because the code in sys.c (hmmm it's been awhile but, I think > that's the module) checked for Sorry, we are not NetBSD. We are doing some things different, and the boot code is certainly among them. The FreeBSD biosboot code only fails for `weird' configurations, e.g. if there are holes in the `wd' disk chain (wd1 missing, so wd2 is BIOS drive 0x81), or for mixed SCSI and ST506 setups. All these cases are covered by the most recent boot code in that you are allowed to establish an arbitrary mapping between BIOS drive numbers and BSD disk names / unit numbers. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)