From owner-freebsd-current Thu Mar 8 9:38:49 2001 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 80BE737B718 for ; Thu, 8 Mar 2001 09:38:47 -0800 (PST) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f28HdqY01512; Thu, 8 Mar 2001 09:39:52 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200103081739.f28HdqY01512@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Randell Jesup Cc: current@FreeBSD.ORG Subject: Re: well! That root didn't work! Let's try another! In-reply-to: Your message of "08 Mar 2001 12:31:10 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Mar 2001 09:39:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As suggested, if the correct root device can't be found, the boot > _should_ offer you a choice of running off others that appear to be > bootable. The "appear to be bootable" criterion is almost impossible (and unsafe to attempt) to determine. Also, I certainly can see instances where someone would want to > have it take an alternate partition to run off of - it could be an > alternate boot behavior programmed into the boot block code at label time. > Note: I don't know exactly what we do now; I'm just taking the above > comments as fact. The current arrangement provides almost maximal flexibility; I find it odd that rather than determining the facts for yourself, you base your comments on an inaccurate reading of a not-very-accurate posting. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message