From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e08bb0gb6Tz2 for ; Fri, 10 Aug 2012 13:12:45 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 10 Aug 2012 13:12:44 +0200 (CEST) Message-ID: <5024ECA8.9050509@redhat.com> Date: Fri, 10 Aug 2012 13:12:40 +0200 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] veritysetup support for files List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wesley Miaw Cc: "dm-crypt@saout.de" On 08/09/2012 07:27 PM, Wesley Miaw wrote: > The result I need is one file that contains a filesystem image (this > would have already been created ahead of time), a second file that > contains the raw hash data for that filesystem image, and a third > file containing the dm-verity table parameters. I am creating the > last file by redirecting veritysetup stdout to a file. Ah, ok. So your only request is that raw hash data image is created automatically as file (if parameter is not a block device directly) and that this file doesn't need to be pre-allocated, correct? I think I can do it even without introducing new library function (I really do not want next context constructor type here). I'll reply once I will have something ready for testing. Milan