From: mgreger@cinci.rr.com
To: "'dm-crypt@saout.de'" <dm-crypt@saout.de>
Subject: Re: [dm-crypt] Two questions
Date: Thu, 14 Nov 2019 02:43:40 +0000 [thread overview]
Message-ID: <92a863b49d487b1bc8b79422a2279ae872139a88@webmail> (raw)
[-- Attachment #1: Type: text/plain, Size: 269 bytes --]
From Arno Wagner, Dr.:
> You may also have sectors in filesystems that are generally the
same and that would be obvious.
Thanks, that's what I was curious about.
> The simple answer is: If you care, then do not do this.
That seems like good advice.
[-- Attachment #2: Type: text/html, Size: 478 bytes --]
next reply other threads:[~2019-11-14 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 2:43 mgreger [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-14 2:45 [dm-crypt] Two questions mgreger
2019-11-13 18:42 mgreger
2019-11-13 23:16 ` Arno Wagner
2019-11-13 15:15 mgreger
2019-11-13 18:07 ` Michael Kjörling
2019-11-14 9:15 ` Ondrej Kozina
2019-11-15 10:00 ` Milan Broz
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=92a863b49d487b1bc8b79422a2279ae872139a88@webmail \
--to=mgreger@cinci.rr.com \
--cc=dm-crypt@saout.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).