summaryrefslogtreecommitdiff
path: root/sbin/fsck_ffs/SMM.doc/2.t
diff options
context:
space:
mode:
Diffstat (limited to 'sbin/fsck_ffs/SMM.doc/2.t')
-rw-r--r--sbin/fsck_ffs/SMM.doc/2.t12
1 files changed, 6 insertions, 6 deletions
diff --git a/sbin/fsck_ffs/SMM.doc/2.t b/sbin/fsck_ffs/SMM.doc/2.t
index ff3aff813f1..faacce041aa 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.4 2003/06/02 20:06:15 millert Exp $
+.\" $OpenBSD: 2.t,v 1.5 2005/02/02 04:36:56 jaredy Exp $
.\" $NetBSD: 2.t,v 1.2 1995/03/18 14:56:08 cgd Exp $
.\"
.\" Copyright (c) 1982, 1993
@@ -124,7 +124,7 @@ and summary information describing the usage of data blocks
within the cylinder group.
A fixed number of inodes is allocated for each cylinder group
when the file system is created.
-The current policy is to allocate one inode for each 2048
+The current policy is to allocate one inode for every 2048
bytes of disk space;
this is expected to be far more inodes than will ever be needed.
.PP
@@ -231,8 +231,8 @@ The disk information is updated to reflect the in-core information
when the buffer is required for another use,
when a
.I sync (2)
-is done (at 30 second intervals) by
-.I "/etc/update" "(8),"
+is done (which happens automatically at 30 second intervals through
+a kernel thread),
or by manual operator intervention with the
.I sync (8)
command.
@@ -256,9 +256,9 @@ The problem with asynchronous inode updates
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
+(i.e. the process blocks until the information is
really written to disk)
when they are being deallocated.
-Similarly inodes are kept consistent by synchronously
+Similarly, inodes are kept consistent by synchronously
deleting, adding, or changing directory entries.
.ds RH Fixing corrupted file systems