Warn about "mount -u" bug.

This commit is contained in:
Dag-Erling Smørgrav 1998-10-16 00:06:56 +00:00
parent 1964f204c9
commit bdd042f095
2 changed files with 10 additions and 2 deletions

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
.\" $Id: mount.8,v 1.22 1998/04/08 18:31:18 wosch Exp $
.\" $Id: mount.8,v 1.23 1998/07/09 05:49:58 jkoshy Exp $
.\"
.Dd June 16, 1994
.Dt MOUNT 8
@ -348,6 +348,10 @@ 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

View File

@ -30,7 +30,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount.8 8.8 (Berkeley) 6/16/94
.\" $Id: mount.8,v 1.22 1998/04/08 18:31:18 wosch Exp $
.\" $Id: mount.8,v 1.23 1998/07/09 05:49:58 jkoshy Exp $
.\"
.Dd June 16, 1994
.Dt MOUNT 8
@ -348,6 +348,10 @@ 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