From owner-freebsd-hackers Mon Jul 1 19:45:51 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FD7F37B400 for ; Mon, 1 Jul 2002 19:45:48 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A944C43E13 for ; Mon, 1 Jul 2002 19:45:47 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id WAA12182; Mon, 1 Jul 2002 22:45:44 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g622jE322614; Mon, 1 Jul 2002 22:45:14 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15649.5050.486714.104483@grasshopper.cs.duke.edu> Date: Mon, 1 Jul 2002 22:45:14 -0400 (EDT) To: Chan Tur Wei Cc: freebsd-hackers@freebsd.org Subject: Re: dual booting current/stable on x86? In-Reply-To: <20020702080738.Q19609-100000@zaapth.twnet.org> References: <15648.54278.323659.18641@grasshopper.cs.duke.edu> <20020702080738.Q19609-100000@zaapth.twnet.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Chan Tur Wei writes: > > I'm not sure how booting with lilo will work (never played with it). > > Instead, I dug around a bit previously, and I found that boot1.s reads: > # > # If we are on a hard drive, then load the MBR and look for the first > # FreeBSD slice. We use the fake partition entry below that points to > # the MBR when we call nread. The first pass looks for the first active > # FreeBSD slice. The second pass looks for the first non-active FreeBSD > # slice if the first one fails. > # > > So unless someone specifically sets the active partition, the 1st FreeBSD > one, usually -stable, will get loaded. Since boot1+boot2 is loaded by the > partition boot boot0, or the standard DOS boot (or, even MS's multi boot > selector), the above may cause the 2nd FreeBSD slice to never get loaded. > > Incidentally, our booteasy (boot0.s) is one such someone. Maybe if lilo > or liloboot does the same thing, it will work too. Excellent. Thanks for the pointer. Now I at least have some understanding of what's happening. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message