From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] [RFC] new target: live filesystem
Date: Mon, 3 Dec 2012 14:07:58 +0100 [thread overview]
Message-ID: <20121203140758.25732492@skate> (raw)
In-Reply-To: <1354531204-17481-1-git-send-email-jeremy.rosen@openwide.fr>
Dear J?r?my Rosen,
On Mon, 3 Dec 2012 11:40:03 +0100, J?r?my Rosen wrote:
> diff --git a/fs/live/live.mk b/fs/live/live.mk
> new file mode 100644
> index 0000000..33fe515
> --- /dev/null
> +++ b/fs/live/live.mk
> @@ -0,0 +1,20 @@
> +#############################################################
> +#
> +# Build the live root filesystem directory
> +#
> +#############################################################
> +
> +
> +define ROOTFS_LIVE_CMD
> + sudo rsync -a --no-o --no-g --delete-during $(TARGET_DIR)/ $(BR2_TARGET_ROOTFS_LIVE_DEST)/
> +endef
Do we really want to include sudo commands in Buildroot? I'm not sure
we want.
What about instead a post-image script hook, that users can use to
extract automatically the tarball image somewhere?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-03 13:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 8:12 [Buildroot] [PATCH] [PATCH][RFC] new target: live filesystem Jérémy Rosen
2012-11-29 23:43 ` [Buildroot] " Arnout Vandecappelle
2012-11-30 9:00 ` Jeremy Rosen
2012-11-30 0:04 ` [Buildroot] [PATCH] " Steve Calfee
2012-11-30 9:15 ` Arnout Vandecappelle
2012-11-30 21:46 ` Steve Calfee
2012-12-03 8:57 ` Jeremy Rosen
2012-12-03 9:21 ` Samuel Martin
2012-12-03 10:21 ` [Buildroot] [PATCH] reorder fs alphabetically Jérémy Rosen
2012-12-03 10:30 ` Jeremy Rosen
2012-12-03 10:40 ` [Buildroot] [PATCH] [RFC] new target: live filesystem Jérémy Rosen
2012-12-03 13:07 ` Thomas Petazzoni [this message]
2012-12-03 13:42 ` Jeremy Rosen
2012-12-05 7:18 ` Arnout Vandecappelle
2012-12-05 7:12 ` Arnout Vandecappelle
2012-12-05 9:28 ` Jeremy Rosen
2012-12-05 17:31 ` Arnout Vandecappelle
2012-12-06 13:22 ` Jeremy Rosen
2012-12-06 13:36 ` Jeremy Rosen
2012-12-06 13:36 ` Jérémy Rosen
2012-12-10 7:11 ` Arnout Vandecappelle
2012-12-10 10:51 ` Jeremy Rosen
2012-12-17 8:58 ` Jeremy Rosen
2012-12-17 12:41 ` Richard Genoud
2012-12-17 16:08 ` Samuel Martin
2012-12-17 16:35 ` Richard Genoud
2013-01-02 17:38 ` Arnout Vandecappelle
2013-01-03 8:54 ` Jeremy Rosen
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=20121203140758.25732492@skate \
--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