All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Genimage last partition size issue
Date: Thu, 26 May 2016 21:59:29 +0200	[thread overview]
Message-ID: <20160526215929.61993c8f@free-electrons.com> (raw)
In-Reply-To: <87bn3s61en.fsf@dell.be.48ers.dk>

Hello,

On Thu, 26 May 2016 21:54:08 +0200, Peter Korsgaard wrote:

> Can dd detect and do something sensible about sparse files? I thought it
> was only able to create sparse files (by seeking)? I would guess you
> need a tool that understand the filesystem to know if you can really
> skip sequences of zeros when writing.

man dd(1):

       sparse try to seek rather than write the output for NUL input blocks

So it doesn't seem to need a sparse file, it's just that it detects
blocks that are completely zero and does not write them.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-05-26 19:59 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
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 [this message]
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=20160526215929.61993c8f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.