From: Tyler Hicks <code@tyhicks.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Doc Mailing List <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-fsdevel@vger.kernel.org, ecryptfs@vger.kernel.org
Subject: Re: [PATCH 13/44] docs: filesystems: convert ecryptfs.txt to ReST
Date: Mon, 17 Feb 2020 14:07:21 -0600 [thread overview]
Message-ID: <20200217200721.GA277681@elm> (raw)
In-Reply-To: <6e13841ebd00c8d988027115c75c58821bb41a0c.1581955849.git.mchehab+huawei@kernel.org>
On 2020-02-17 17:11:59, Mauro Carvalho Chehab wrote:
> - Add a SPDX header;
> - Add a document title;
> - use :field: markup;
> - Some whitespace fixes and new line breaks;
> - Mark literal blocks as such;
> - Add table markups;
> - Add it to filesystems/index.rst.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Acked-by: Tyler Hicks <code@tyhicks.com>
This serves as a reminder that eCryptfs document is in serious need of
some updates. Thanks!
Tyler
> ---
> .../{ecryptfs.txt => ecryptfs.rst} | 44 ++++++++++++-------
> Documentation/filesystems/index.rst | 1 +
> 2 files changed, 28 insertions(+), 17 deletions(-)
> rename Documentation/filesystems/{ecryptfs.txt => ecryptfs.rst} (70%)
>
> diff --git a/Documentation/filesystems/ecryptfs.txt b/Documentation/filesystems/ecryptfs.rst
> similarity index 70%
> rename from Documentation/filesystems/ecryptfs.txt
> rename to Documentation/filesystems/ecryptfs.rst
> index 01d8a08351ac..7236172300ef 100644
> --- a/Documentation/filesystems/ecryptfs.txt
> +++ b/Documentation/filesystems/ecryptfs.rst
> @@ -1,14 +1,18 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +
> +======================================================
> eCryptfs: A stacked cryptographic filesystem for Linux
> +======================================================
>
> eCryptfs is free software. Please see the file COPYING for details.
> For documentation, please see the files in the doc/ subdirectory. For
> building and installation instructions please see the INSTALL file.
>
> -Maintainer: Phillip Hellewell
> -Lead developer: Michael A. Halcrow <mhalcrow@us.ibm.com>
> -Developers: Michael C. Thompson
> - Kent Yoder
> -Web Site: http://ecryptfs.sf.net
> +:Maintainer: Phillip Hellewell
> +:Lead developer: Michael A. Halcrow <mhalcrow@us.ibm.com>
> +:Developers: Michael C. Thompson
> + Kent Yoder
> +:Web Site: http://ecryptfs.sf.net
>
> This software is currently undergoing development. Make sure to
> maintain a backup copy of any data you write into eCryptfs.
> @@ -19,13 +23,15 @@ SourceForge site:
> http://sourceforge.net/projects/ecryptfs/
>
> Userspace requirements include:
> - - David Howells' userspace keyring headers and libraries (version
> - 1.0 or higher), obtainable from
> - http://people.redhat.com/~dhowells/keyutils/
> - - Libgcrypt
>
> +- David Howells' userspace keyring headers and libraries (version
> + 1.0 or higher), obtainable from
> + http://people.redhat.com/~dhowells/keyutils/
> +- Libgcrypt
>
> -NOTES
> +
> +Notes
> +=====
>
> In the beta/experimental releases of eCryptfs, when you upgrade
> eCryptfs, you should copy the files to an unencrypted location and
> @@ -33,20 +39,21 @@ then copy the files back into the new eCryptfs mount to migrate the
> files.
>
>
> -MOUNT-WIDE PASSPHRASE
> +Mount-wide Passphrase
> +=====================
>
> Create a new directory into which eCryptfs will write its encrypted
> files (i.e., /root/crypt). Then, create the mount point directory
> -(i.e., /mnt/crypt). Now it's time to mount eCryptfs:
> +(i.e., /mnt/crypt). Now it's time to mount eCryptfs::
>
> -mount -t ecryptfs /root/crypt /mnt/crypt
> + mount -t ecryptfs /root/crypt /mnt/crypt
>
> You should be prompted for a passphrase and a salt (the salt may be
> blank).
>
> -Try writing a new file:
> +Try writing a new file::
>
> -echo "Hello, World" > /mnt/crypt/hello.txt
> + echo "Hello, World" > /mnt/crypt/hello.txt
>
> The operation will complete. Notice that there is a new file in
> /root/crypt that is at least 12288 bytes in size (depending on your
> @@ -59,10 +66,13 @@ keyctl clear @u
> Then umount /mnt/crypt and mount again per the instructions given
> above.
>
> -cat /mnt/crypt/hello.txt
> +::
>
> + cat /mnt/crypt/hello.txt
>
> -NOTES
> +
> +Notes
> +=====
>
> eCryptfs version 0.1 should only be mounted on (1) empty directories
> or (2) directories containing files only created by eCryptfs. If you
> diff --git a/Documentation/filesystems/index.rst b/Documentation/filesystems/index.rst
> index c6885c7ef781..d6d69f1c9287 100644
> --- a/Documentation/filesystems/index.rst
> +++ b/Documentation/filesystems/index.rst
> @@ -59,6 +59,7 @@ Documentation for filesystem implementations.
> cramfs
> debugfs
> dlmfs
> + ecryptfs
> fuse
> overlayfs
> virtiofs
> --
> 2.24.1
>
next prev parent reply other threads:[~2020-02-17 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:11 [PATCH 00/44] Manually convert filesystem FS documents to ReST Mauro Carvalho Chehab
2020-02-17 16:11 ` [PATCH 13/44] docs: filesystems: convert ecryptfs.txt " Mauro Carvalho Chehab
2020-02-17 20:07 ` Tyler Hicks [this message]
2020-02-18 4:01 ` [PATCH 00/44] Manually convert filesystem FS documents " Matthew Wilcox
2020-02-18 10:04 ` Mauro Carvalho Chehab
2020-02-19 9:32 ` Jonathan Corbet
2020-02-19 15:11 ` Mauro Carvalho Chehab
2020-03-02 21:13 ` Jonathan Corbet
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=20200217200721.GA277681@elm \
--to=code@tyhicks.com \
--cc=corbet@lwn.net \
--cc=ecryptfs@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
/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).