From owner-freebsd-questions@FreeBSD.ORG Fri Aug 5 03:24:27 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC87716A41F for ; Fri, 5 Aug 2005 03:24:27 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from opusnet.com (mail.opusnet.com [209.210.200.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 900A043D45 for ; Fri, 5 Aug 2005 03:24:27 +0000 (GMT) (envelope-from garys@opusnet.com) Received: from localhost.localhost [70.98.246.232] by opusnet.com with ESMTP (SMTPD32-8.05) id ABE18D460102; Thu, 04 Aug 2005 20:24:17 -0700 Received: from localhost.localhost (localhost.localhost [127.0.0.1]) by localhost.localhost (8.13.3/8.13.3) with ESMTP id j753Q4Ki054777; Thu, 4 Aug 2005 20:26:04 -0700 (PDT) (envelope-from garys@opusnet.com) Received: (from jojo@localhost) by localhost.localhost (8.13.3/8.13.3/Submit) id j753PqVo054776; Thu, 4 Aug 2005 20:25:52 -0700 (PDT) (envelope-from garys@opusnet.com) To: Michael Dexter References: From: garys@opusnet.com (Gary W. Swearingen) Date: Thu, 04 Aug 2005 20:25:52 -0700 In-Reply-To: (Michael Dexter's message of "Fri, 5 Aug 2005 00:56:16 +0300") Message-ID: <8doe8d12v3.e8d@mail.opusnet.com> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@freebsd.org Subject: Re: 5.x separate /boot slice? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2005 03:24:28 -0000 Michael Dexter writes: >>> I would like to try a separate /boot slice as permitted by FreeBSD 5.x... I forget where you got that from. Anyway, the boot(8) manpage makes it pretty clear that your /boot must be on the "a" of whatever "s" you're booting, but I'm not as sure as others that you can't get the loader to then boot up a kernel from that /boot but using some other "/" on another "s", probably on its "a". I'd be investigating /boot/defaults/loader.conf and its #currdev="disk1s1a" # Set the current device #root_disk_unit="0" # Force the root disk unit number #rootdev="disk1s1a" # Set the root filesystem and/or how to execute the "built-in" loader(8) commands, like "unload", "set currdev", etc. It sounds like that's possible (something about "exec"ing in scripts), but you might have to learn a bit of "Forth". Try booting to the loader command line, and try to get it to use a kernel+modules from one "s" and a "/" from another. loader(8)'s "boot_askname" sounds encouraging.