Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6853 ; Fri, 15 Jan 93 10:37:20 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!ariel.ucs.unimelb.EDU.AU!werple.apana.org.au!pos!posgate!sleeper!raz From: raz@sleeper.apana.org.au (Roland Turner) Newsgroups: comp.unix.bsd Subject: Re: 386BSD.EXE - Let DOS handle booting? Message-ID: <C0xKpq.2IC@sleeper.apana.org.au> Date: Sat, 16 Jan 1993 05:03:25 GMT References: <C0q94w.48p@NeoSoft.com> <1993Jan13.102710.26478@nessie.mcc.ac.uk> Organization: Desolation Road Railfan BBS Lines: 22 ade@nessie.mcc.ac.uk (Adrian Collins) writes: >In <C0q94w.48p@NeoSoft.com> karl@NeoSoft.com (Karl Lehenbauer) writes: >>Hey, how about making the second stage boot, say Julian's loader, an >>executable DOS program? >[Stuff Deleted] >>The only drawback is you'd need a DOS partition or floppy to do it that >>way, no biggie but possibly offensive to purists. >And extra RAM to have DOS and the resident part of the command-line >interpreter resident in memory. Not at all. Load them low and load the kernel high. Presumably the kernel won't need to be altered to support this (assuming that in a future release loading above 1M will be the norm) and thus it will quietly trash the DOS space as soon as it gets control. Then again, we could get really fancy and save the DOS context, ala Netware 3.x :-)