summaryrefslogtreecommitdiff
path: root/sbin/fsck_ffs/SMM.doc/2.t
diff options
context:
space:
mode:
authorTodd T. Fries <todd@cvs.openbsd.org>2002-06-09 08:13:10 +0000
committerTodd T. Fries <todd@cvs.openbsd.org>2002-06-09 08:13:10 +0000
commit3ed8b10a8df515c0cb5a2a6a0962c67f1c697164 (patch)
tree16644eb4e4232e2d2cd65fc342c5dbaafdc4e136 /sbin/fsck_ffs/SMM.doc/2.t
parentc021608bd50b74de1b8074e336f7adad03b1c7d8 (diff)
rm trailing whitespace
Diffstat (limited to 'sbin/fsck_ffs/SMM.doc/2.t')
-rw-r--r--sbin/fsck_ffs/SMM.doc/2.t6
1 files changed, 3 insertions, 3 deletions
diff --git a/sbin/fsck_ffs/SMM.doc/2.t b/sbin/fsck_ffs/SMM.doc/2.t
index 99abe88af54..f5e10314c8b 100644
--- a/sbin/fsck_ffs/SMM.doc/2.t
+++ b/sbin/fsck_ffs/SMM.doc/2.t
@@ -1,4 +1,4 @@
-.\" $OpenBSD: 2.t,v 1.2 1996/06/23 14:30:37 deraadt Exp $
+.\" $OpenBSD: 2.t,v 1.3 2002/06/09 08:13:06 todd Exp $
.\" $NetBSD: 2.t,v 1.2 1995/03/18 14:56:08 cgd Exp $
.\"
.\" Copyright (c) 1982, 1993
@@ -213,7 +213,7 @@ the order that the update
requests were being honored must first be understood.
.PP
When a user program does an operation to change the file system,
-such as a
+such as a
.I write ,
the data to be written is copied into an internal
.I "in-core"
@@ -257,7 +257,7 @@ which inode should really claim the block.
A similar problem can arise with a multiply claimed inode.
.PP
The problem with asynchronous inode updates
-can be avoided by doing all inode deallocations synchronously.
+can be avoided by doing all inode deallocations synchronously.
Consequently,
inodes and indirect blocks are written to the disk synchronously
(\fIi.e.\fP the process blocks until the information is