From owner-freebsd-questions@FreeBSD.ORG Thu Aug 4 21:00:58 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 A7E7816A41F for ; Thu, 4 Aug 2005 21:00:58 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52D0543D46 for ; Thu, 4 Aug 2005 21:00:58 +0000 (GMT) (envelope-from list-freebsd-2004@morbius.sent.com) Received: from frontend3.messagingengine.com (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 8F541CC92E3 for ; Thu, 4 Aug 2005 17:00:53 -0400 (EDT) X-Sasl-enc: s+DzQ6zDeAV2zn+8Z2qY4Xab3wLpmCk2nPkluefmtL6D 1123189253 Received: from gumby.localdomain (dsl-80-41-65-21.access.as9105.com [80.41.65.21]) by frontend3.messagingengine.com (Postfix) with ESMTP id 9EBA51E5 for ; Thu, 4 Aug 2005 17:00:53 -0400 (EDT) From: RW To: freebsd-questions@freebsd.org Date: Thu, 4 Aug 2005 22:00:51 +0100 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508042200.51875.list-freebsd-2004@morbius.sent.com> 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: Thu, 04 Aug 2005 21:00:58 -0000 On Thursday 04 August 2005 09:49, Michael Dexter wrote: > Hello, > > I would like to try a separate /boot slice as permitted by FreeBSD 5.x... > > (http://www.khmere.com/freebsd_book/html/ch08.html) > > But alas it does not appear to be as simple as simply specifying a > /boot during setup. This causes the bootloader to complain about not > finding a kernel given that /boot on the root partition is empty. > Presumably this is too early in the boot process to link /boot > to the /boot slice given that the fstab has not been read yet. > > Any pointers on how to get this to work? > > Perhaps the boot loader needs to be pointed at the /boot slice rather > than root and a "rootdev" variable fed into a specific loader stage? > I'm not sure! Search the list. This comes up about once a month, and I've yet to see anyone succeed. Aside from "it's the way Linux does it", do you have any good reason for wanting this?