From: Colin Walters <walters@verbum.org>
To: Yevhen Kyriukha <kirgene@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Create btrfs subvolume during image building
Date: Tue, 02 Jul 2013 09:29:22 -0400 [thread overview]
Message-ID: <1372771762.3791.50.camel@localhost> (raw)
In-Reply-To: <CADV-EXEu9adLK7ArMTZv30gTdppzPwMpNMC1JPpVhSm9jQqTag@mail.gmail.com>
On Tue, 2013-07-02 at 15:04 +0300, Yevhen Kyriukha wrote:
> Hi!
>
>
> I'd like to create image with btrfs rootfs partition.
> I want to store all files on separate subvolume on btrfs partition.
> For this purpose I'm creating *.bbclass that simply extends IMAGE_CMD.
>
>
> The problem is that to create btrfs subvolume I need to mount it
> first, but only root can execute "mount".
Another option is libguestfs; recent versions support btrfs.
prev parent reply other threads:[~2013-07-02 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 12:04 Create btrfs subvolume during image building Yevhen Kyriukha
2013-07-02 12:19 ` Sander van Grieken
2013-07-02 13:29 ` Colin Walters [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=1372771762.3791.50.camel@localhost \
--to=walters@verbum.org \
--cc=kirgene@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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