Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!spool.mu.edu!agate!tfs.com!tfs.com!julian
From: julian@tfs.com (Julian Elischer)
Subject: Re: Booting 386bsd from 2nd hard drive (sorry)
Message-ID: <1992Oct19.054343.11599@tfs.com>
Organization: TRW Financial Systems
References: <9210190237.AA18397@deepthought.cs.utexas.edu>
Date: Mon, 19 Oct 1992 05:43:43 GMT
Lines: 42
In article <9210190237.AA18397@deepthought.cs.utexas.edu> STDN%MARIST@VM.MARIST.EDU (Dan Newcombe) writes:
>Sorry to bring this topic up again, but I didn't pay attention last
>time as it didn't matter then but does now. (NEW DRIVE :)
>
>So, if someone could post a summary to me on how to do this,
>it'd be great.
> -Dan
I have been working with one gentleman (the name escapes me)
to tailor the new bootblocks to allow them to be used on a second drive.
(two simple changes)
apparently the os2 bootmanager can boot a partition from the second
drive. If the new bootblocks are loaded on the second drive, then
they can carry on from there and successfully boot
a kernel from there.
the tricky bit is finding some way of loading the bootblocks from the
second drive. Once they are loaded they can handle the situation.
As suggested above, the os2 bootmanager seems to be able to perform
the trick (that is what the gentleman in question was using).
What do you want to put on the first drive?
If you can afford it, making a small root on the first drive
may be the simplest thing, (and there are performance advantages)
If I could get hold of the author of the os-bs code I
would like to discuss with him adding support for the
second drive to his bootblock.
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@tfs.com +------>x USA \ in a very strange
| ( OZ ) 2118 Milvia st. Berkeley CA. \___ ___ | country !
+- X_.---._/ USA+(510) 704-3137(wk) \_/ \\
v