From: Sami Kerola <kerolasa@iki.fi>
Date: Thu, 13 Apr 2017 10:18:58 +0000 (+0100)
Subject: docs: try to convince open(2) O_DIRECT rather than using raw device
X-Git-Tag: v2.30-rc1~28^2~6
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=abec3cb1de6c9721110571a918e642df9eda6e73;p=thirdparty%2Futil-linux.git

docs: try to convince open(2) O_DIRECT rather than using raw device

Tell in manual page that one should use open(2) O_DIRECT flag rather than
raw device.

Signed-off-by: Sami Kerola <kerolasa@iki.fi>
---

diff --git a/disk-utils/raw.8 b/disk-utils/raw.8
index 717f4ef1bb..5a3b96e3ce 100644
--- a/disk-utils/raw.8
+++ b/disk-utils/raw.8
@@ -88,6 +88,10 @@ 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!
+.SH NOTES
+Rather than using raw devices applications should prefer
+.BR open (2)
+devices, such as /dev/sda1, with the O_DIRECT flag.
 .SH AUTHOR
 Stephen Tweedie (sct@redhat.com)
 .SH AVAILABILITY