From: Somchai Smythe <buraphalinuxserver@gmail.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: dm-devel@redhat.com, lvm-devel@redhat.com
Subject: Re: [linux-lvm] LVM release 2.02.96 / git / veritysetup
Date: Sat, 9 Jun 2012 18:00:42 +0700 [thread overview]
Message-ID: <CAFJqGkPHjaCXPq4zYxHp_koMwxbku0w=1W0wNznM_nEnpGaUGg@mail.gmail.com> (raw)
In-Reply-To: <4FD30CF2.8060505@redhat.com>
Do not package LVM release 2.02.96 at all, or just the verity stuff?
On 6/9/12, Milan Broz <mbroz@redhat.com> wrote:
> On 06/09/2012 02:23 AM, Alasdair G Kergon wrote:
>> veritysetup
>> -----------
>> Although this release contains a userspace tool for dm-verity,
>> configure --with-verity-setup=<cryptlib>
>> we think the cryptsetup package would provide a better home for this
>> so watch out for an updated version in an upcoming cryptsetup release.
>
> Please do not use this version except for experiments and do not package
> it in distributions yet.
>
> Superblock format will perhaps change a little bit and also veritysetup
> utility
> from cryptsetup source will use different command syntax (similar to
> dmsetup
> and cryptsetup) and get full library support through libcryptsetup.
>
> The code is maintained in separate veritysetup branch in cryptsetup git
> for now, once it get back all features it will be merged to main branch
> (next week).
> http://code.google.com/p/cryptsetup/source/browse/?name=veritysetup
>
> Milan
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2012-06-09 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 0:23 [linux-lvm] LVM release 2.02.96 / git / veritysetup Alasdair G Kergon
2012-06-09 8:44 ` Milan Broz
2012-06-09 11:00 ` Somchai Smythe [this message]
2012-06-09 12:28 ` Alasdair G Kergon
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='CAFJqGkPHjaCXPq4zYxHp_koMwxbku0w=1W0wNznM_nEnpGaUGg@mail.gmail.com' \
--to=buraphalinuxserver@gmail.com \
--cc=dm-devel@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm-devel@redhat.com \
/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).