From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] fs/cpio: add option to manually specify file list
Date: Fri, 16 Feb 2018 23:51:35 +0100 [thread overview]
Message-ID: <20180216235135.248cc872@windsurf.lan> (raw)
In-Reply-To: <20171026191627.18949-2-sconnor@lynx.com>
Hello,
On Thu, 26 Oct 2017 12:16:27 -0700, Seamus Connor wrote:
> For some systems it may be desireable to have an initramfs that is
> smaller than the full root filesystem. This commit adds support for
> creating an initramfs based on a manually specified set of files. It is
> up to the user to define a sensible set of files. This file list could
> either be statically created, or it could be created as the result of a
> pre-fs hook script.
>
> Signed-off-by: Seamus Connor <sconnor@lynx.com>
Considering the replies from both Yann and Arnout who were both not
very convinced by the approach, and Arnout's idea of using a fakeroot
script to achieve the same thing in a more flexible way, I've marked
this patch as Rejected in our patch tracking system.
Best regards,
Thomas Petazzoni
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-16 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Multiple root filesystems for single kernel/toolchain>
2017-10-26 19:16 ` [Buildroot] [PATCH 0/1] fs/cpio: add option to manually specify file list Seamus Connor
2017-10-26 19:16 ` [Buildroot] [PATCH 1/1] " Seamus Connor
2017-10-26 20:13 ` Seamus Connor
2018-01-01 11:54 ` Thomas Petazzoni
2018-01-01 13:22 ` Yann E. MORIN
2018-01-01 14:47 ` Thomas Petazzoni
2018-02-06 14:55 ` Sam Voss
2018-02-06 23:30 ` Arnout Vandecappelle
2018-02-16 22:51 ` Thomas Petazzoni [this message]
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=20180216235135.248cc872@windsurf.lan \
--to=thomas.petazzoni@bootlin.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