From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Genimage last partition size issue
Date: Thu, 26 May 2016 20:41:57 +0200 [thread overview]
Message-ID: <20160526204157.201c0d78@free-electrons.com> (raw)
In-Reply-To: <57474262.2020500@zacarias.com.ar>
Hello,
On Thu, 26 May 2016 15:37:22 -0300, Gustavo Zacarias wrote:
> >> How should genimage know what the size is of your SD card when you
> >> generate the foo.img image? I guess you would need to add size = 4G
> >> inside image foo.img { }, but notice that this is isn't very efficient
> >> as you will be writing lots of zeros to the sd card.
> >
> > Isn't it possible to generate a sparse file, and then use the sparse
> > capability of dd to avoid writing those lots of zeros?
> >
> > Thomas
>
> You're still dealing with the partition table, it goes beyond sparse files.
Well, I was thinking of really creating a 4 GB image file when you have
a 4 GB SD card, so that the partition table is exactly in the state it
will be on the SD card. But by using sparse files, the 4 GB image file
isn't really taking up 4 GB on your disk, and you don't have to dd the
entire 4 GB, since zeros can be skipped.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-26 18:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 15:26 [Buildroot] Genimage last partition size issue Matthew Weber
2016-05-24 15:56 ` Peter Korsgaard
2016-05-26 17:42 ` Matthew Weber
2016-05-26 17:49 ` Gustavo Zacarias
2016-05-26 18:35 ` Thomas Petazzoni
2016-05-26 18:37 ` Gustavo Zacarias
2016-05-26 18:41 ` Thomas Petazzoni [this message]
2016-05-26 18:45 ` Gustavo Zacarias
2016-05-26 19:18 ` Thomas Petazzoni
2016-05-26 19:19 ` Gustavo Zacarias
2016-05-26 19:55 ` Peter Korsgaard
2016-05-26 19:54 ` Peter Korsgaard
2016-05-26 19:59 ` Thomas Petazzoni
2016-05-26 20:05 ` Peter Korsgaard
2016-05-26 21:08 ` Yann E. MORIN
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=20160526204157.201c0d78@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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