From owner-freebsd-questions Mon Nov 17 05:37:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA11210 for questions-outgoing; Mon, 17 Nov 1997 05:37:53 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from localhost.localdomain (pm3bl1-37.csrlink.net [207.44.9.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA11202 for ; Mon, 17 Nov 1997 05:37:45 -0800 (PST) (envelope-from rknebel@localhost.localdomain) Received: (from rknebel@localhost) by localhost.localdomain (8.8.4/8.8.4) id IAA01201; Mon, 17 Nov 1997 08:41:05 -0500 Message-ID: <19971117084105.13183@localhost.localdomain> Date: Mon, 17 Nov 1997 08:41:05 -0500 From: Rick Knebel To: questions@freebsd.org Subject: upgrade question References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Doug White on Mon, Nov 17, 1997 at 12:49:14AM -0800 Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I have just upgraded from 2.2.2 to 2.2.5 with the help of some people from this list without difficulty. One stange thing happened though and I was curious if anyone had any ideas. I have two hard drives. #1 has OS2 and linux aand number 2 has freebsd. I use the os2 boot manager to boot my different OS's. When I was done with the upgrade it told me to remove the floopy and then reboot. When I did this it would go through my typical boot process but then right before boot manager would come up, I would get a prompt that said press any key to reboot. I had to use my os2 bootup disc and what solved the problem was reinstalling os2 boot manager. Everything worked fine after that. Can anyone think of a reason why this upgrade should give me this problem when boot manager is not on the same disc as freebsd. Thanks Alot -- Rick Knebel rknebel@mail.csrlink.net