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 03/12] Manual pages: raw.8: Minor formatting and wording fixes
Date: Fri, 24 Jul 2020 12:06:09 +0200 [thread overview]
Message-ID: <20200724100618.584918-3-mtk.manpages@gmail.com> (raw)
In-Reply-To: <20200724100618.584918-1-mtk.manpages@gmail.com>
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
disk-utils/raw.8 | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/disk-utils/raw.8 b/disk-utils/raw.8
index ba9fd256a..d569507b8 100644
--- a/disk-utils/raw.8
+++ b/disk-utils/raw.8
@@ -34,10 +34,10 @@ device numbers, or as a path name
to an existing block device file.
.PP
The bindings already in existence can be queried with the
-.I \-q
+.B \-q
option, which is used either with a raw device filename to query that one
device, or with the
-.I \-a
+.B \-a
option to query all bound raw devices.
.PP
Unbinding can be done by specifying major and minor 0.
@@ -66,8 +66,8 @@ will query an existing binding instead of setting a new one.
.TP
\fB\-a\fR, \fB\-\-all\fR
With
-.B \-q
-, specify that all bound raw devices should be queried.
+.BR \-q ,
+specify that all bound raw devices should be queried.
.TP
\fB\-h\fR, \fB\-\-help\fR
Display help text and exit.
@@ -78,20 +78,23 @@ Display version information and exit.
.SH NOTES
Rather than using raw devices applications should prefer
.BR open (2)
-devices, such as /dev/sda1, with the O_DIRECT flag.
+devices, such as
+.IR /dev/sda1 ,
+with the
+.B O_DIRECT
+flag.
.SH BUGS
The Linux
.BR dd (1)
command should be used without the \fBbs=\fR option, or the blocksize
needs to be a multiple of the sector size of the device (512 bytes usually),
otherwise it will fail with "Invalid Argument" messages (EINVAL).
-
.PP
Raw I/O devices do not maintain cache coherency with the Linux block
device buffer cache. If you use raw I/O to overwrite data already in
the buffer cache, the buffer cache will no longer correspond to the
contents of the actual storage device underneath. This is deliberate,
-but is regarded either a bug or a feature depending on who you ask!
+but is regarded as either a bug or a feature, depending on who you ask!
.SH AUTHORS
Stephen Tweedie (sct@redhat.com)
.SH AVAILABILITY
--
2.26.2
next prev parent reply other threads:[~2020-07-24 10:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 10:06 [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 02/12] Manual pages: fsck.cramfs.8: Wording fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` Michael Kerrisk (man-pages) [this message]
2020-07-24 10:06 ` [PATCH 04/12] Manual pages: sfdisk.8: Minor wording and formatting fixes Michael Kerrisk (man-pages)
2020-07-24 16:32 ` Nuno Silva
2020-08-27 15:16 ` Michael Kerrisk
2020-08-28 11:09 ` Nuno Silva
2020-07-24 10:06 ` [PATCH 05/12] Manual pages: sfdisk.8: Use less aggressive indenting Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 06/12] Manual pages: lslogins.1: Minor wording and formatting fixres Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 07/12] Manual pages: nologin.8: formatting fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 08/12] Manual pages: logger.1: minor formatting and typo fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 09/12] Manual pages: lsblk.8: Minor " Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 10/12] Manual pages: wdctl.8: typo fix Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 11/12] Manual pages: agetty.8: Minor formatting and wording fixes Michael Kerrisk (man-pages)
2020-07-24 10:06 ` [PATCH 12/12] Manual pages: wipefs.8: Formatting fixes Michael Kerrisk (man-pages)
2020-07-24 12:43 ` [PATCH 01/12] Manual pages: blockdev.8: Minor wording and formatting fixes Karel Zak
2020-07-24 16:07 ` Nuno Silva
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=20200724100618.584918-3-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).