From: trebol <trebol55555@aol.com>
To: 9fans@9fans.net
Subject: [9fans] cryptsetup
Date: Mon, 27 May 2013 15:42:11 +0000 [thread overview]
Message-ID: <51a37ed3.Cv/84Y4LD0KmwkHM%trebol55555@aol.com> (raw)
Hello everyone,
I have problems in a new installed system with cryptsetup and cwfs64.
checktag pc=8694 cw "/dev/fs/fscache"w'/dev/fs/fsworm" (17cc8) tag /path=Tfile/49361; expected Tdir/49358
This is a fresh installation (not strange move-copy-dump-whatever) so this tags inconsistencies are worrying me,
because that can happen in the future again with important data.
Anyone has have similar problems with cryptsetup and cwfs64?
Can I trust cryptsetup?
Is fossil more stable than cwfs64? I have read a lot in 9fans archive but I can't make any conclusion...
Also, I don't find anything about cryptsetup outside 9front. Is it possible to use it in the original Plan9?
Thanks in advance,
trebol.
next reply other threads:[~2013-05-27 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 15:42 trebol [this message]
2013-05-27 20:05 ` erik quanstrom
2013-05-27 21:15 trebol
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=51a37ed3.Cv/84Y4LD0KmwkHM%trebol55555@aol.com \
--to=trebol55555@aol.com \
--cc=9fans@9fans.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 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).