From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DA4Jn-00068b-GK
	for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:58:03 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DA4D2-0005cR-Ci
	for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:51:08 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DA4Cx-0005UU-5T
	for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:50:59 -0500
Received: from [64.233.184.198] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DA3uK-0007G1-O3
	for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:31:44 -0500
Received: by wproxy.gmail.com with SMTP id 36so672999wri
	for <qemu-devel@nongnu.org>; Sat, 12 Mar 2005 02:31:43 -0800 (PST)
Message-ID: <aec7e5c305031202314ffce2cf@mail.gmail.com>
Date: Sat, 12 Mar 2005 11:31:43 +0100
From: Magnus Damm <magnus.damm@gmail.com>
Subject: Re: [Qemu-devel] gentoo disk image for QEmu
In-Reply-To: <1110621349.28647.6.camel@penguin>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <1110228937.3297.18.camel@penguin>
	<aec7e5c305030713262d1227cc@mail.gmail.com>
	<1110621349.28647.6.camel@penguin>
Reply-To: Magnus Damm <magnus.damm@gmail.com>, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?J=E9r=F4me_Bouat?= <jerome.bouat@wanadoo.fr>
Cc: qemu-devel@nongnu.org

Hello again,

On Sat, 12 Mar 2005 10:55:49 +0100, J=E9r=F4me Bouat
<jerome.bouat@wanadoo.fr> wrote:
> Here is what did my scripts in order to install the bootloader :
> ---
> /sbin/losetup $(loop_device_2) $(disk_image).tmp && \
> mount -t proc none $(tree)/proc && \
> $(chroot) $(tree) /bin/bash install_grub.sh && \
> /sbin/losetup -d $(loop_device_2) && \
> ---
>=20
> with 'install_grub.sh':
> ---
> /usr/sbin/env-update && source /etc/profile &&
> echo using this device map for GRUB: &&
> echo --- &&
> cat dev.map &&
> echo --- &&
> grub --device-map=3Ddev.map <<END
> root (hd0,0)
> setup (hd0)
> END
> ---
>=20
> But it never worked. Could your tool help me ?

Grub is not included in my tool, so I guess it won't help you in this
case. But feel free to add grub and send a patch to me. =3D)

Have you tried executing the commands one by one to see exectly where
things fail? Verify that the chrooted environment has all the required
device nodes and libraries.

/ magnus