Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Dargaud <dargaud@lpsc.in2p3.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Creating a bootable filesystem image?
Date: Tue, 15 Apr 2008 10:35:36 +0200	[thread overview]
Message-ID: <028d01c89ed3$b035e7f0$ad289e86@LPSC0173W> (raw)
In-Reply-To: 326f33790804141009iadec986u91a1abbde904bbf1@mail.gmail.com

I normally just use dd to transfer the filesystem image onto a larger one.
Say you have /dev/sdc2 which is 500Mb and rootfs.powerpc.ext2 which is 10Mb 
like in my case. I just do
dd if=rootfs.powerpc.ext2 of=/dev/sdc2

There may be some hidden problems with that, but I never ran into them. Even 
a subsequent chkdsk runs without errors (you'd assume it would at least tell 
you the free space is missreported).

If you really want an ext2 at a specific size, just do the opposite:
dd if=/dev/sdc2 of=- | bzip2 > test.ext2.bz2

You may be able to use a loopback mount to do this, but I haven't tried it.
-- 
Guillaume Dargaud
http://www.gdargaud.net/

  reply	other threads:[~2008-04-15  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 19:11 [Buildroot] Creating a bootable filesystem image? Sam Liddicott
2008-04-14 16:57 ` Arun Reddy
2008-04-14 17:09   ` Arun Reddy
2008-04-15  8:35     ` Guillaume Dargaud [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-14 20:29 Sam Liddicott
2008-04-14 22:31 ` Arun Reddy
2008-04-07 20:07 Sam Liddicott
2008-04-07 23:30 ` Arun Reddy
2008-04-07 18:58 Arun Reddy
2008-04-07 19:29 ` John Voltz
2008-04-08 10:02 ` Sebastian
     [not found]   ` <326f33790804081325s680eb37bg9b8e73663277f4c2@mail.gmail.com>
     [not found]     ` <47FBE4A8.9080104@arcor.de>
2008-04-08 22:26       ` Arun Reddy
     [not found]         ` <47FBF3F3.4040001@arcor.de>
2008-04-08 23:50           ` Arun Reddy
     [not found]             ` <47FCD648.8040007@arcor.de>
2008-04-11 18:51               ` Arun Reddy

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='028d01c89ed3$b035e7f0$ad289e86@LPSC0173W' \
    --to=dargaud@lpsc.in2p3.fr \
    --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