Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bogdan Cristea <cristeab@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Creating a filesystem for QEMU
Date: Thu, 12 Nov 2009 17:03:07 +0200	[thread overview]
Message-ID: <200911121703.07478.cristeab@gmail.com> (raw)
In-Reply-To: <4d28d4b50911120658h67155758k54a7d95599cee1fe@mail.gmail.com>

On Thursday 12 November 2009 16:58:15 you wrote:
>   - You can generate a cloop root filesystem using buildroot, and then
>    convert it to the format you want using qemu-img
>    - Create an initramfs, and boot it using qemu
>    - Create an ext2 filesystem and write it on a qemu disk through an
>    install cdrom
>    - and so on....
> 
   Thank you for your feedback, I'll try to explore these options in the next 
days. IMHO it could be extremely useful to have these indications into the 
help page of buildroot.
   Could you expand a little more the last option (Create an ext2 filesystem 
and write it on a qemu disk through an install cdrom). I don't understand that 
part.

thanks
Bogdan

  reply	other threads:[~2009-11-12 15:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12 14:23 [Buildroot] Creating a filesystem for QEMU Bogdan Cristea
2009-11-12 14:58 ` Lionel Landwerlin
2009-11-12 15:03   ` Bogdan Cristea [this message]
2009-11-12 15:14     ` Lionel Landwerlin
2009-11-12 15:22     ` Mark Constable
2009-11-12 15:04 ` Chris Packham
     [not found] ` <4AFC1FC8.3020305@gmail.com>
2009-11-13 13:18   ` Bogdan Cristea
2009-11-13 13:56     ` Lionel Landwerlin
2009-11-13 13:57       ` Lionel Landwerlin
2009-11-13 14:03         ` Chris Packham
2009-11-13 14:10           ` Lionel Landwerlin
     [not found]     ` <a038bef50911130559i31605c47k57d27e91d95b28f8@mail.gmail.com>
2009-11-13 14:46       ` Bogdan Cristea
2009-11-13 15:14         ` Chris Packham
2009-11-13 17:45           ` Bogdan Cristea

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=200911121703.07478.cristeab@gmail.com \
    --to=cristeab@gmail.com \
    --cc=buildroot@busybox.net \
    /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