From owner-freebsd-questions@FreeBSD.ORG Sat Dec 13 14:58:39 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A88731065673 for ; Sat, 13 Dec 2008 14:58:39 +0000 (UTC) (envelope-from robin@reportlab.com) Received: from pih-relay08.plus.net (pih-relay08.plus.net [212.159.14.20]) by mx1.freebsd.org (Postfix) with ESMTP id 6C87D8FC17 for ; Sat, 13 Dec 2008 14:58:39 +0000 (UTC) (envelope-from robin@reportlab.com) Received: from [87.114.66.149] (helo=[192.168.0.3]) by pih-relay08.plus.net with esmtp (Exim) id 1LBVwz-0005Tf-Dk for freebsd-questions@freebsd.org; Sat, 13 Dec 2008 14:58:37 +0000 Message-ID: <4943CD9C.6040909@jessikat.plus.net> Date: Sat, 13 Dec 2008 14:58:36 +0000 From: Robin Becker User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <493D246C.80008@chamonix.reportlab.co.uk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: accb14648dd2d786a66895f5ce536867 Subject: Re: install freebsd from inside another operating system 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: Sat, 13 Dec 2008 14:58:39 -0000 My experiments with the depenguinator seem to show it has a hidden dependency on the partition used for the constructed disk image. On my ubuntu 8.10 the original install constructed /dev/sda1 /dev/sda2 extended /dev/sda5 swap Not sure why the extended, but it wasn't really needed so I deleted sda5 & sda2 and then created a new primary partition /dev/sda2 for the swap. When using /dev/sda5 grub gave an error 12: invalid device, now with exactly the same build process /dev/sda2 gives a boot that works. However, the result crashes when the next stage kicks in. I don't know where the dependency is, perhaps it must use a primary partition or perhaps there's some way to specify the boot device that's not being used. The bootcode is fixed and not a function of the boot target (which is suspicious). -- Robin Becker