From owner-freebsd-questions Mon Nov 18 17:13:47 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA02598 for questions-outgoing; Mon, 18 Nov 1996 17:13:47 -0800 (PST) Received: from raptor.icubed.net (root@raptor.icubed.net [205.138.34.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA02593 for ; Mon, 18 Nov 1996 17:13:41 -0800 (PST) Received: from LOCALNAME (ppp22.icubed.net) by raptor.icubed.net (4.1/SMI-4.1) id AA12939; Mon, 18 Nov 96 20:12:16 EST Date: Mon, 18 Nov 96 20:12:16 EST Message-Id: <9611190112.AA12939@raptor.icubed.net> X-Sender: smorri59@mailhost.icubed.net X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: questions@FreeBSD.org From: ScottMorris Subject: Re: Multiple disk install w/bootmanager Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk I just got the message that Jordan was out of the office so I am forwarding this to the questions list per the instructions in his vac. file. Thanks for any assistance anyone can lend on this. Scott Morris >Date: Mon, 18 Nov 1996 20:06:57 >To: "Jordan K. Hubbard" >From: ScottMorris >Subject: Re: Multiple disk install w/bootmanager > >At 09:07 AM 11/11/96 -0800, you wrote: >>> I am attempting to load FreeBSD onto my second hard drive (wd1), DOS >>> is the first drive (wd0). The partion builds fine and everything installs >> >>The partition editor will show you a disk selection screen. Select >>wd0 and don't change anything but select the boot manager installation >>in the screen that follows after you say (Q)uit. > > Fine to this point...everything works as expected and documented. > >>Then go on to wd1 and lay it out for FreeBSD. > > When the partition is laid out for wd1 it throws me back to the bootmanager screen and no matter what selection I make (I have tried every combination) the boot manager is not installed onto c where it belongs.... I am prepared to boot from the floppy if necessary, to get this up. Is there another procedure I can use or is the infinate bootmanager loop a bug. > I appreciate your prompt reply to my previous message and look forward to any input you can give me on this. The system being installed on is a AT&T P-75, Phoenix BIOS V4.04, and the boot block is not write protected. > >> >> Jordan >> > > ----- Scott L. Morris Systems Security Consultant smorri59@icubed.net Data Forensics Finger smorri59@ally.ios.com for my pgp public key.