From bf1a22744135bd30c8c4cefc3b9376bd3449e19c Mon Sep 17 00:00:00 2001 From: Alfred Perlstein Date: Tue, 22 Feb 2000 01:40:43 +0000 Subject: [PATCH] Don't scare the users. Kirk argees that the comment about corruption caused by switching the flags on an already mounted manpage are bogus, it doesn't happen. Ok by: mckusick --- sbin/mount/mount.8 | 4 ---- sbin/mount_ifs/mount.8 | 4 ---- 2 files changed, 8 deletions(-) diff --git a/sbin/mount/mount.8 b/sbin/mount/mount.8 index 935816b092ed..510fb3ce05cb 100644 --- a/sbin/mount/mount.8 +++ b/sbin/mount/mount.8 @@ -361,10 +361,6 @@ file system table .Xr umount 8 .Sh BUGS It is possible for a corrupted file system to cause a crash. -.Pp -Switching a filesystem back and forth between asynchronous and normal -operation or between read/write and read/only access using ``mount --u'' may gradually bring about severe filesystem corruption. .Sh CAVEATS After a successful mount, the permissions on the original mount point determine if diff --git a/sbin/mount_ifs/mount.8 b/sbin/mount_ifs/mount.8 index 935816b092ed..510fb3ce05cb 100644 --- a/sbin/mount_ifs/mount.8 +++ b/sbin/mount_ifs/mount.8 @@ -361,10 +361,6 @@ file system table .Xr umount 8 .Sh BUGS It is possible for a corrupted file system to cause a crash. -.Pp -Switching a filesystem back and forth between asynchronous and normal -operation or between read/write and read/only access using ``mount --u'' may gradually bring about severe filesystem corruption. .Sh CAVEATS After a successful mount, the permissions on the original mount point determine if