qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jérôme Bouat" <jerome.bouat@wanadoo.fr>
To: Magnus Damm <magnus.damm@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] gentoo disk image for QEmu
Date: Sat, 12 Mar 2005 10:55:49 +0100	[thread overview]
Message-ID: <1110621349.28647.6.camel@penguin> (raw)
In-Reply-To: <aec7e5c305030713262d1227cc@mail.gmail.com>

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) && \
---

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=dev.map <<END
root (hd0,0)
setup (hd0)
END
---

But it never worked. Could your tool help me ?

Le lundi 07 mars 2005 à 22:26 +0100, Magnus Damm a écrit :
> Hello,
> 
> On Mon, 07 Mar 2005 21:55:36 +0100, Jérôme Bouat
> <jerome.bouat@wanadoo.fr> wrote:
> > I would generate a Gentoo Linux disk image for QEmu.
> > 
> > This source based Linux distro can be configurated to generate hardware
> > specific binaries through its package management system.
> > 
> > I previously tried with Bochs. Therefore, I wrote some scripts. The main
> > part of the generation was made in a Linux chrooted environment on a
> > real host which was compatible with the emulated host. The disk image
> > generation was blocked by the boot loader installation step.
> 
> I'm not sure I understand your question. Is the problem that the
> chrooted environment was unable to install a bootloader for the target
> system?
> 
> I've hacked up a filesystem manipulation tool that is available for download at:
> 
> http://www.smallworks.com/~jim/fsimage/
> 
> The tool is actually a shell script and a small x86 distribution that
> together are used to access filesystems independent of root access or
> host kernel configuration. Needless to say, the tool depends on QEMU.
> 0.6.1 or newer.
> 
> I am not sure if the tool is of interest for you, but maybe it helps.
> 
> / magnus
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

  parent reply	other threads:[~2005-03-12 10:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 20:55 [Qemu-devel] gentoo disk image for QEmu Jérôme Bouat
2005-03-07 21:26 ` Magnus Damm
2005-03-08  1:51   ` [Qemu-devel] ESC key problems & keyboard problems Paulo R. Dallan
2005-03-09 11:16     ` Oliver Gerlich
2005-03-09 18:44       ` Paulo R. Dallan
2005-03-10 22:52         ` [Qemu-devel] Still some keyboard problems (was: ESC key problems & keyboard problems) Paulo R. Dallan
2005-03-12 21:33           ` [Qemu-devel] Still some keyboard problems Oliver Gerlich
2005-03-12  9:55   ` Jérôme Bouat [this message]
2005-03-12 10:31     ` [Qemu-devel] gentoo disk image for QEmu Magnus Damm
2005-04-01 13:05 ` [Qemu-devel] x86 emulated hardware : which make.conf options ? Jérôme Bouat
2005-04-01 13:14   ` Karel Gardas
2005-04-01 17:26   ` Natalia Portillo
2005-04-01 18:04     ` Paul Brook
2005-04-02 16:38       ` Natalia Portillo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1110621349.28647.6.camel@penguin \
    --to=jerome.bouat@wanadoo.fr \
    --cc=magnus.damm@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).