From owner-freebsd-current  Sun Jul 27 19:21:08 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id TAA04217
          for current-outgoing; Sun, 27 Jul 1997 19:21:08 -0700 (PDT)
Received: from dfw-ix5.ix.netcom.com (dfw-ix5.ix.netcom.com [206.214.98.5])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA04198
          for <current@FreeBSD.ORG>; Sun, 27 Jul 1997 19:20:57 -0700 (PDT)
Received: (from smap@localhost)
          by dfw-ix5.ix.netcom.com (8.8.4/8.8.4)
	  id VAA08077; Sun, 27 Jul 1997 21:20:24 -0500 (CDT)
Received: from scz-ca5-19.ix.netcom.com(199.182.129.179) by dfw-ix5.ix.netcom.com via smap (V1.3)
	id sma007848; Sun Jul 27 21:19:31 1997
Message-ID: <33DC01B5.167EB0E7@ix.netcom.com>
Date: Sun, 27 Jul 1997 19:19:33 -0700
From: Sherwin <sherwink@ix.netcom.com>
X-Mailer: Mozilla 3.01Gold (X11; U; FreeBSD 2.2.2-RELEASE i386)
MIME-Version: 1.0
To: current@FreeBSD.ORG
Subject: Multiple FreeBSD Systems on a Single Disk
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

I installed 2.2.2 in the first partition of my disk. It was previously a
Linux partition. I have 2.2.1 installed in the second partition. It is
all still there, I can mount it and access it, but I do not know how to
boot it. Boot-Easy gives the same result for both F1 and F2, it boots
the 2.2.2 partition.

While there is no great harm, if I can no longer run 2.2.1, I would love
to find a solution, so that I can experiment with 3.0 Snap, and still
have 2.2.2 to fall back on. I have searched the documentation for an
answer, particularily NextBoot, but nothing seems to explain this
behavior. Please ket me know what I am overlooking. 

Thanks :-)