Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 6 Mar 2016 17:39:26 +0000 (UTC)
From:      Jason Helfman <jgh@FreeBSD.org>
To:        doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org
Subject:   svn commit: r48347 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics
Message-ID:  <201603061739.u26HdQV6064675@repo.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: jgh
Date: Sun Mar  6 17:39:25 2016
New Revision: 48347
URL: https://svnweb.freebsd.org/changeset/doc/48347

Log:
  - improve readability
  
  Submitted by:	Chris Petrik
  Differential Revision:	https://reviews.freebsd.org/D5557 (based on)

Modified:
  head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml

Modified: head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml	Sun Mar  6 14:44:58 2016	(r48346)
+++ head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml	Sun Mar  6 17:39:25 2016	(r48347)
@@ -385,12 +385,17 @@ Closing device "echo".</screen>
       block-devices almost unusable, or at least dangerously
       unreliable.  The caching will reorder the sequence of write
       operations, depriving the application of the ability to know the
-      exact disk contents at any one instant in time.  This makes
-      predictable and reliable crash recovery of on-disk data
-      structures (filesystems, databases etc.) impossible.  Since
+      exact disk contents at any one instant in time.</para>
+
+    <para>
+      This makes predictable and reliable crash recovery of on-disk
+      data structures (filesystems, databases etc.) impossible.  Since
       writes may be delayed, there is no way the kernel can report to
       the application which particular write operation encountered a
-      write error, this further compounds the consistency problem.
+      write error, this further compounds the consistency
+      problem.</para>
+
+    <para>
       For this reason, no serious applications rely on block devices,
       and in fact, almost all applications which access disks directly
       take great pains to specify that character (or



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201603061739.u26HdQV6064675>