From: Grant Edwards <grant.b.edwards@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] tar rootfs compression and copy-image-to don't work together?
Date: Wed, 12 May 2010 15:45:18 +0000 (UTC) [thread overview]
Message-ID: <hseied$naf$1@dough.gmane.org> (raw)
If I enable building a tar rootfs with gzip compression and configure
buildroot to copy the image to /tftpboot, the tar file that gets
copied to /tftboot isn't compressed.
There is a compressed tar file in output/images, but buildroot copies
the _uncompressed_ tar file to /tftpboot.
Is this a bug, or am I misunderstanding the configuration options?
--
Grant Edwards grant.b.edwards Yow! I am NOT a nut....
at
gmail.com
reply other threads:[~2010-05-12 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='hseied$naf$1@dough.gmane.org' \
--to=grant.b.edwards@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 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.