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

Also, in the synopis mention -F separately to make it more obvious that
it applies only to -A, swap two options to make a line more similar to
the preceding one, and improve some wording.

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

diff --git a/sys-utils/mount.8.adoc b/sys-utils/mount.8.adoc
index f4a704556..bb4151225 100644
--- a/sys-utils/mount.8.adoc
+++ b/sys-utils/mount.8.adoc
@@ -47,15 +47,16 @@ mount - mount a filesystem
 
 *mount* [*-l*] [*-t* _fstype_]
 
-*mount* *-a* [*-fFnrsvw*] [*-t* _fstype_] [*-O* _optlist_]
+*mount* *-a* [*-F*] [*-fnrsvw*] [*-t* _fstype_] [*-O* _optlist_]
 
 *mount* [*-fnrsvw*] [*-o* _options_] _device_|_mountpoint_
 
-*mount* [*-fnrsvw*] [*-t* _fstype_] [*-o* _options_] _device mountpoint_
+*mount* [*-fnrsvw*] [*-o* _options_] [*-t* _fstype_] _device mountpoint_
 
 *mount* *--bind*|*--rbind*|*--move* _olddir newdir_
 
-*mount* *--make-*[*shared*|*slave*|*private*|*unbindable*|*rshared*|*rslave*|*rprivate*|*runbindable*] _mountpoint_
+*mount* *--make-*[*r*]{*shared*|*slave*|*private*|*unbindable*} _mountpoint_
+
 
 == DESCRIPTION
 
@@ -765,8 +766,8 @@ Note that *mount*(8) still sanitizes and canonicalizes the source and target pat
 *X-mount.noloop*::
 Do not create and mount a loop device, even if the source of the mount is a regular file.
 
-*X-mount.subdir=*__directory__::
-Allow mounting sub-directory from a filesystem instead of the root directory. For now, this feature is implemented by temporary filesystem root directory mount in unshared namespace and then bind the sub-directory to the final mount point and umount the root of the filesystem. The sub-directory mount shows up atomically for the rest of the system although it is implemented by multiple *mount*(2) syscalls.
+**X-mount.subdir=**_directory_::
+Allow mounting a sub-directory of a filesystem instead of the root directory. For now, this feature is implemented by a temporary filesystem root-directory mount in an unshared namespace and then binding the sub-directory to the final mount point and unmounting the root of the filesystem. The sub-directory mount shows up atomically for the rest of the system although it is implemented by multiple *mount*(2) syscalls.
 +
 Note that this feature will not work in session with an unshared private mount namespace (after *unshare --mount*) on old kernels or with *mount*(8) without support for file-descriptors-based mount kernel API. In this case, you need *unshare --mount --propagation shared*.
 +
@@ -1513,7 +1514,7 @@ Set behavior on error:
 *panic*;;
 If an error is encountered, cause a kernel panic.
 
-[**lock**|**umount**|*repair*];;
+**lock**|**umount**|*repair*;;
 These mount options don't do anything at present; when an error is encountered only a console message is printed.
 
 === Mount options for umsdos
@@ -1590,7 +1591,7 @@ Parity bytes for FEC (default: 2). Optional.
 **verity.roothashsig=**__path__::
 Path to *pkcs7*(1ssl) signature of root hash hex string. Requires crypt_activate_by_signed_key() from cryptsetup and kernel built with *CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG*. For device reuse, signatures have to be either used by all mounts of a device or by none. Optional.
 
-**verity.oncorruption=**__ignore__|__restart__|__panic__::
+**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.
-- 
2.48.1


  parent reply	other threads:[~2025-04-07 15:16 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 ` [PATCH 6/8] mount: (man) fix some indentation issues, and improve a few wordings Benno Schulenberg
2025-04-07 15:14 ` Benno Schulenberg [this message]
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-7-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