[src/trunk]: src/bin/rm Fix typo.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/7807192392c0
branches:  trunk
changeset: 557523:7807192392c0
user:      wiz <wiz%NetBSD.org@localhost>
date:      Sun Jan 11 09:41:55 2004 +0000

description:
Fix typo.

diffstat:

 bin/rm/rm.c |  6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diffs (27 lines):

diff -r 9478b07b0e0b -r 7807192392c0 bin/rm/rm.c
--- a/bin/rm/rm.c       Sun Jan 11 09:40:36 2004 +0000
+++ b/bin/rm/rm.c       Sun Jan 11 09:41:55 2004 +0000
@@ -1,4 +1,4 @@
-/* $NetBSD: rm.c,v 1.41 2004/01/11 02:17:12 tls Exp $ */
+/* $NetBSD: rm.c,v 1.42 2004/01/11 09:41:55 wiz Exp $ */
 
 /*-
  * Copyright (c) 1990, 1993, 1994, 2003
@@ -39,7 +39,7 @@
 #if 0
 static char sccsid[] = "@(#)rm.c       8.8 (Berkeley) 4/27/95";
 #else
-__RCSID("$NetBSD: rm.c,v 1.41 2004/01/11 02:17:12 tls Exp $");
+__RCSID("$NetBSD: rm.c,v 1.42 2004/01/11 09:41:55 wiz Exp $");
 #endif
 #endif /* not lint */
 
@@ -346,7 +346,7 @@
  *
  * Furthermore, the presence of track caches, disk and controller write
  * caches, and so forth make it extremely difficult to ensure that data
- * have actuolly been written to the disk, particularly when one tries
+ * have actually been written to the disk, particularly when one tries
  * to repeatedly overwrite the same sectors in quick succession.  We call
  * fsync(), but controllers with nonvolatile cache, as well as IDE disks
  * that just plain lie about the stable storage of data, will defeat this.