From: Kyungmin Park <kmpark@infradead.org>
To: "Evgeny A. Marchenko" <xengine@mail.ru>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Question: Build btrfs filesystem from specific directory.
Date: Sat, 12 Jun 2010 13:47:52 +0900 [thread overview]
Message-ID: <AANLkTinZkD1HOCOk1DnFkCnGoXDCr7N4s4OCact1t_Pn@mail.gmail.com> (raw)
In-Reply-To: <201006120633.12043.xengine@mail.ru>
Hi,
On Sat, Jun 12, 2010 at 11:33 AM, Evgeny A. Marchenko <xengine@mail.ru>=
wrote:
>> I'm founding the solution to build btrfs filesystem image from
>> specific directory.
>> it's common concept at mobile build environment.
>> e.g., ubifs and cramfs support this feature.
>>
>> In case of ubifs
>> -r, -d, --root=3DDIR =A0 =A0 =A0 build file system from directory DI=
R
>> In case of cramfs
>> dirname =A0 =A0root of the filesystem to be compressed
>>
>> But btrfs doesn't support it.
> Maybe because btrfs is not a compressed read-only filesystem
It's just example. it's not matter to support compressed or not.
>
>> So does it have any plan to support this feature at btrfs?
> You can create file-backed loop device, mount it and copy the directo=
ry
> contents there. Than unmount the loop and voila - you have btrfs imag=
e
Right, I used it now, but some build machine doesn't have or support
btrfs, it mean can't mount btrfs as loopback.
I just want to create btrfs image from directory without any host
machine dependency such as kernel version and whatever.
To simply, just use the mkfs.btrfs itself.
Thank you,
Kyungmin Park
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-06-12 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-12 2:20 Question: Build btrfs filesystem from specific directory Kyungmin Park
2010-06-12 2:33 ` Evgeny A. Marchenko
2010-06-12 4:47 ` Kyungmin Park [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=AANLkTinZkD1HOCOk1DnFkCnGoXDCr7N4s4OCact1t_Pn@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=xengine@mail.ru \
/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;
as well as URLs for NNTP newsgroup(s).