From owner-freebsd-ppc Thu Feb 20 5:44:46 2003 Delivered-To: freebsd-ppc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 643C337B405; Thu, 20 Feb 2003 05:44:43 -0800 (PST) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FACF43FA3; Thu, 20 Feb 2003 05:44:42 -0800 (PST) (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.12.6/8.12.6) with ESMTP id h1KDif8I022421 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 20 Feb 2003 08:44:41 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h1KDiaa48133; Thu, 20 Feb 2003 08:44:36 -0500 (EST) (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: <15956.56260.218671.830134@grasshopper.cs.duke.edu> Date: Thu, 20 Feb 2003 08:44:36 -0500 (EST) To: Peter Grehan Cc: Sean_Welch@alum.wofford.org, freebsd-ppc@FreeBSD.ORG Subject: Re: Also interested in testing In-Reply-To: <3E547309.F538CED9@freebsd.org> References: <5035103.1045689625512.JavaMail.nobody@fozzie.psp.pas.earthlink.net> <15955.63196.87405.422505@grasshopper.cs.duke.edu> <3E547309.F538CED9@freebsd.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-ppc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Grehan writes: > > In fact, when I was playing with this, the loader couldn't really pass > > the root device to the kernel either, since you need to specify the > > root device in OFW syntax (<30 chars or so of hex and device names>), > > not FreeBSD syntax (ad0s10). So in either case, the kernel would > > stop and ask for its root. > > This has to be fixed, but in the meantime, at the loader prompt you can issue > something like: > > > set vfs.root.mountfrom=ufs:ad0s11 > > and then boot. Yes, of course. But its shorter to type ufs:ad0s11 at the mountroot prompt ;) What's the prognosis for the loader learning enough about HFS or HFS+ to be able to pull its configuration from files? Alternatively, I wonder if we could teach the OS-X boot loader about FFS so that it could load the loader from a FFS partition, and the loader could remain blissfully ignorant about HFS. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ppc" in the body of the message