Util-Linux package development
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@telfort.nl>
To: util-linux@vger.kernel.org
Subject: [PATCH 6/8] mount: (man) fix some indentation issues, and improve a few wordings
Date: Mon,  7 Apr 2025 17:14:37 +0200	[thread overview]
Message-ID: <20250407151503.23394-6-bensberg@telfort.nl> (raw)
In-Reply-To: <20250407151503.23394-1-bensberg@telfort.nl>

Signed-off-by: Benno Schulenberg <bensberg@telfort.nl>
---
 sys-utils/mount.8.adoc | 31 ++++++++++++++++++++-----------
 1 file changed, 20 insertions(+), 11 deletions(-)

diff --git a/sys-utils/mount.8.adoc b/sys-utils/mount.8.adoc
index 5103b91c5..f4a704556 100644
--- a/sys-utils/mount.8.adoc
+++ b/sys-utils/mount.8.adoc
@@ -567,6 +567,7 @@ mount -t tmpfs none /mnt -o \
 ....
 ____
 
++
 For more details, see *selinux*(8).
 
 *defaults*::
@@ -746,6 +747,7 @@ and xfs.
 Note that comma is used as a separator between mount options, it means
 that auto-fstypes values have to be properly quoted, don’t forget that the shell
 strips off quotes and thus double quoting is required. For example:
++
 ____
 mount -t auto -o'X-mount.auto-fstypes="noext2,ext3"'  /dev/sdc1 /mnt/test
 ____
@@ -933,17 +935,23 @@ Set the umask applied to directories only. The default is the umask of the curre
 Set the umask applied to regular files only. The default is the umask of the current process. The value is given in octal.
 
 **allow_utime=**__value__::
-This option controls the permission check of mtime/atime.
+This option controls the permission check of mtime/atime.  Possible values:
 
 *20*;;
-If current process is in group of file's group ID, you can change timestamp.
-
+If the current process is in the group of the file's group ID,
+you can change the timestamp.
++
 *2*;;
-Other users can change timestamp.
+Other users can change the timestamp.
 
-The default is set from 'dmask' option. (If the directory is writable, *utime*(2) is also allowed. I.e. ~dmask & 022)
-
-Normally *utime*(2) checks that the current process is owner of the file, or that it has the *CAP_FOWNER* capability. But FAT filesystems don't have UID/GID on disk, so the normal check is too inflexible. With this option you can relax it.
++
+The default is set from the above *dmask* option. (If the directory
+is writable, *utime*(2) is also allowed.  That is: ~dmask & 022.)
+ +
+Normally *utime*(2) checks that the current process is the owner of the
+file, or that it has the *CAP_FOWNER* capability. But FAT filesystems
+don't have UID/GID on disk, so the normal check is too inflexible.
+With this option you can relax it.
 
 **check=**__value__::
 Three different levels of pickiness can be chosen:
@@ -1584,11 +1592,11 @@ Path to *pkcs7*(1ssl) signature of root hash hex string. Requires crypt_activate
 
 **verity.oncorruption=**__ignore__|__restart__|__panic__::
 Instruct the kernel to ignore, reboot or panic when corruption is detected. By default the I/O operation simply fails. Requires Linux 4.1 or newer, and libcrypsetup 2.3.4 or newer. Optional.
-
++
 Supported since util-linux v2.35.
-
-For example commands:
-
++
+For example, the commands:
++
 ....
 mksquashfs /etc /tmp/etc.raw
 veritysetup format /tmp/etc.raw /tmp/etc.verity --root-hash-file=/tmp/etc.roothash
@@ -1598,6 +1606,7 @@ mount -o verity.hashdevice=/tmp/etc.verity,verity.roothashfile=/tmp/etc.roothash
 verity.roothashsig=/tmp/etc.roothash.p7s /tmp/etc.raw /mnt
 ....
 
++
 create squashfs image from _/etc_ directory, verity hash device and mount verified filesystem image to _/mnt_. The kernel will verify that the root hash is signed by a key from the kernel keyring if roothashsig is used.
 
 == LOOP-DEVICE SUPPORT
-- 
2.48.1


  parent reply	other threads:[~2025-04-07 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 15:14 [PATCH 1/8] setarch: (man) remove a synopsis line that mistakenly mentions `arch` Benno Schulenberg
2025-04-07 15:14 ` [PATCH 2/8] choom: (man) add the missing SYNOPSIS section header, and improve wording Benno Schulenberg
2025-04-07 15:14 ` [PATCH 3/8] hexdump: (man) normalize the synopsis, and shrink a list and two tables Benno Schulenberg
2025-04-07 15:14 ` [PATCH 4/8] blkzone: (man) reduce two overblown tables to legible proportions Benno Schulenberg
2025-04-07 15:14 ` [PATCH 5/8] eject: (man) add the missing SYNOPSIS header Benno Schulenberg
2025-04-07 15:14 ` Benno Schulenberg [this message]
2025-04-07 15:14 ` [PATCH 7/8] mount: (man) shorten an overlong line, and improve some markup Benno Schulenberg
2025-04-07 15:14 ` [PATCH 8/8] column: (man) fix broken markup, and improve other markup and wordings Benno Schulenberg
2025-04-08 10:33 ` [PATCH 1/8] setarch: (man) remove a synopsis line that mistakenly mentions `arch` Karel Zak
2025-04-08 12:35   ` Chris Hofstaedtler
2025-04-08 13:24     ` Karel Zak
2025-04-09  9:36   ` Benno Schulenberg
2025-04-08 10:47 ` Karel Zak

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=20250407151503.23394-6-bensberg@telfort.nl \
    --to=bensberg@telfort.nl \
    --cc=util-linux@vger.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