All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] btrfs-progs: new package
Date: Wed, 30 Apr 2014 00:01:15 +0200	[thread overview]
Message-ID: <5360212B.20504@mind.be> (raw)
In-Reply-To: <535FDC9F.70805@zacarias.com.ar>

On 29/04/14 19:08, Gustavo Zacarias wrote:
> On 04/29/2014 01:56 PM, Yann E. MORIN wrote:
> 
>> This should also "depends on BR2_USE_MMU".
> 
> Ooops, i'll add it up.
> 
>> Would it make sense to add them as host-tools, too?
> 
> Not really IMHO.
> Grub2 can in theory understand btrfs, but that would be realistically
> speaking a x86/amd64-only thing.
> And then btrfs-progs AFAIK doesn't include any tool to create images
> like genext2fs does, it talks directly with block devices.
> Sudo with loopback is a bit dangerous and off the charts i think.

 Still, it may be useful to add it as a Config.host option, for use in
post-image scripts (which may indeed have sudo).

 Regards,
 Arnout

> Regards.
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2014-04-29 22:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:49 [Buildroot] [PATCH] btrfs-progs: new package Gustavo Zacarias
2014-04-29 16:56 ` Yann E. MORIN
2014-04-29 17:08   ` Gustavo Zacarias
2014-04-29 17:13     ` Yann E. MORIN
2014-04-29 22:01     ` Arnout Vandecappelle [this message]
2014-04-30 13:36       ` Gustavo Zacarias

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=5360212B.20504@mind.be \
    --to=arnout@mind.be \
    --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.