Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.com.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs: allow extra arguments to common tarball extraction
Date: Sun, 10 Jun 2018 20:48:34 -0300 (BRT)	[thread overview]
Message-ID: <2108507643.2044026.1528674514845.JavaMail.zimbra@datacom.com.br> (raw)
In-Reply-To: <20180608210641.GF2090@scaer>

> From: "Yann Morin" <yann.morin.1998@free.fr>
> To: "Arnout Vandecappelle" <arnout@mind.be>
> Cc: "DATACOM" <casantos@datacom.com.br>, "Thomas De Schampheleire" <thomas.de_schampheleire@nokia.com>, "buildroot"
> <buildroot@buildroot.org>
> Sent: Friday, June 8, 2018 6:06:41 PM
> Subject: Re: [Buildroot] [PATCH] fs: allow extra arguments to common tarball extraction

> Arnout, Carlos, All,
[...]
> And as an example of a split-var filesytem, see the attached br2-external
> tree. It ultimagtely creates $(BINARIES_DIR)/rootfs.meh, a squashfs
> image of /) and $(BINARIES_DIR)/rootfs.meh-var.tar, a tarball of /var.
> The only missing pieve is the runtime startup scripts that will format
> the on-board partition, extact /var.tar in there, and mount it.

Thanks for your example. I transformed it on an example of what I'm
attempting to achieve. Please use the contents of the attached file as
a br2_external and use the defconfig contained there; then run

    $ make rootfs-cpio rootfs-var-{lib,log}-ext4

It will create three image files files under $(BINARIES_DIR): rootfs.cpio,
rootfs.var-lib.ext4 and rootfs.var-log-ext4.

If you apply on buildroot the patch contained there the names will be
rootfs.cpio, rootfs-var-lib.ext4 and rootfs-var-log.ext4, which looks
better, IMO.

Extracting rootfs.common.tar for rootfs-var-log-ext4 is a waste of time
and disk space, since it creates an empty filesystem. Perhaps we could
add a BR2_TARGET_ROOTFS_<FOO>_START_EMPTY knob for filesystems that
populate $(TARGET_DIR) by themselves.

The example does not install a /etc/fstab with entries for /var/lib and
/var/log but of it would be necessary in a real system, of course.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
?Marched towards the enemy, spear upright, armed with the certainty
that only the ignorant can have.? ? Epitaph of a volunteer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br2-multi-fs.tar.xz
Type: application/x-xz-compressed-tar
Size: 3780 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180610/2beefde8/attachment.bin>

  reply	other threads:[~2018-06-10 23:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03  2:21 [Buildroot] [PATCH] fs: allow extra arguments to common tarball extraction Carlos Santos
2018-06-05 17:23 ` Yann E. MORIN
2018-06-06 12:46   ` Carlos Santos
2018-06-06 18:51     ` Yann E. MORIN
2018-06-07 21:03       ` Arnout Vandecappelle
2018-06-07 23:12         ` Carlos Santos
2018-06-08  7:48           ` Arnout Vandecappelle
2018-06-08 17:34             ` Yann E. MORIN
2018-06-08 19:58               ` Arnout Vandecappelle
2018-06-08 17:26           ` Yann E. MORIN
2018-06-09  1:06             ` Carlos Santos
2018-06-09  7:31               ` Yann E. MORIN
2018-06-08 17:19         ` Yann E. MORIN
2018-06-08 19:59           ` Arnout Vandecappelle
2018-06-08 21:06             ` Yann E. MORIN
2018-06-10 23:48               ` Carlos Santos [this message]
2018-06-09  0:58         ` Carlos Santos
2018-10-26 11:43           ` Peter Korsgaard

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=2108507643.2044026.1528674514845.JavaMail.zimbra@datacom.com.br \
    --to=casantos@datacom.com.br \
    --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