From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 09/10] Manual pages: umount.8: use "filesystem" consistently
Date: Thu, 28 May 2020 16:58:23 +0200 [thread overview]
Message-ID: <20200528145823.978508-9-mtk.manpages@gmail.com> (raw)
In-Reply-To: <20200528145823.978508-1-mtk.manpages@gmail.com>
Currently, this page has a mix of "filesystem" and file system",
with the former being predominant. Let's settle on one.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
sys-utils/umount.8 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/sys-utils/umount.8 b/sys-utils/umount.8
index c56e51e18..f04746211 100644
--- a/sys-utils/umount.8
+++ b/sys-utils/umount.8
@@ -24,7 +24,7 @@
.\"
.TH UMOUNT 8 "July 2014" "util-linux" "System Administration"
.SH NAME
-umount \- unmount file systems
+umount \- unmount filesystems
.SH SYNOPSIS
.B umount \-a
.RB [ \-dflnrv ]
@@ -43,13 +43,13 @@ umount \- unmount file systems
.SH DESCRIPTION
The
.B umount
-command detaches the mentioned file system(s) from the file hierarchy. A
-file system is specified by giving the directory where it has been
-mounted. Giving the special device on which the file system lives may
+command detaches the mentioned filesystem(s) from the file hierarchy. A
+filesystem is specified by giving the directory where it has been
+mounted. Giving the special device on which the filesystem lives may
also work, but is obsolete, mainly because it will fail in case this
device was mounted on more than one directory.
.PP
-Note that a file system cannot be unmounted when it is 'busy' - for
+Note that a filesystem cannot be unmounted when it is 'busy' - for
example, when there are open files on it, or when some process has its
working directory there, or when a swap file on it is in use. The
offending process could even be
--
2.26.2
next prev parent reply other threads:[~2020-05-28 14:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:58 [PATCH 01/10] Manual pages: unshare.1: EXAMPLES: improve persistent mount namespace example Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 02/10] Manual pages: unshare.1: typo fix Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 03/10] Manual pages: setpriv.1: Minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 04/10] Manual pages: mount.8, umount.8: Clarify that "namespace" means "mount namespace" Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 05/10] Manual pages: mount.8, umount.8: Consistently format pathnames with italic Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 06/10] Manual pages: mount.8: SEE ALSO: add some obvious references Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 07/10] Manual pages: mount.8: Typo fix (remove an accidental paragraph break) Michael Kerrisk (man-pages)
2020-05-28 14:58 ` [PATCH 08/10] Manual pages: mount.8: Rewrite FILESYSTEM-SPECIFIC MOUNT OPTIONS intro Michael Kerrisk (man-pages)
2020-05-28 14:58 ` Michael Kerrisk (man-pages) [this message]
2020-05-29 7:46 ` [PATCH 01/10] Manual pages: unshare.1: EXAMPLES: improve persistent mount namespace example Karel Zak
2020-05-29 8:54 ` John Paul Adrian Glaubitz
2020-05-29 12:43 ` Karel Zak
2020-05-29 13:22 ` Michael Kerrisk
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=20200528145823.978508-9-mtk.manpages@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kzak@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).