Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6759 ; Tue, 12 Jan 93 19:04:12 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!cs.utexas.edu!sun-barr!olivea!uunet!psinntp!ficc!peter From: peter@ferranti.com (peter da silva) Newsgroups: comp.unix.bsd Subject: Re: 386BSD.EXE - Let DOS handle booting? Message-ID: <id.XVPW.NGG@ferranti.com> Date: 14 Jan 93 22:34:01 GMT References: <C0q94w.48p@NeoSoft.com> <id.QJNW._89@ferranti.com> <1j27i2INNijr@life.ai.mit.edu> Organization: Xenix Support, FICC Lines: 23 In article <1j27i2INNijr@life.ai.mit.edu> mycroft@hal.gnu.ai.mit.edu (Charles Hannum) writes: > In article <id.QJNW._89@ferranti.com> peter@ferranti.com (peter da > silva) writes: > > bootbsd as1a:386bsd.old > > bootbsd -large wd0a > > bootbsd -debug fd0a > Julian's replacement boot blocks already do something similar to this. Interactively, right? They don';t allow something like this: initvga bootbsd as1a:386bsd.old Note that here I'm initialising the VGA card using some proprietary software, then booting off the second SCSI device. I may not even *have* a BSD boot block on the first SCSI device, and may be reading this from my alternate boot floppy. -- Peter da Silva `-_-' Ferranti International Controls Corporation 'U` Sugar Land, TX 77487-5012 USA +1 713 274 5180 "Zure otsoa besarkatu al duzu gaur?"