Reviewed by: various.

Ever since I first say the way the mount flags were used I've hated the
fact that modes, and events, internal and exported, and short-term
and long term flags are all thrown together. Finally it's annoyed me enough..
This patch to the entire FreeBSD tree adds a second mount flag word
to the mount struct. it is not exported to userspace. I have moved
some of the non exported flags over to this word. this means that we now
have 8 free bits in the mount flags. There are another two that might
well move over, but which I'm not sure about.
The only user visible change would have been in pstat -v, except
that davidg has disabled it anyhow.
I'd still like to move the state flags and the 'command' flags
apart from each other.. e.g. MNT_FORCE really doesn't have the
same semantics as MNT_RDONLY, but that's left  for another day.

1 files changed, 2 insertions, 3 deletions

diff --git a/lib/libc/sys/mount.2 b/lib/libc/sys/mount.2
index 00af2cf..d1199c2 100644
--- a/lib/libc/sys/mount.2
+++ b/lib/libc/sys/mount.2
@@ -79,6 +79,8 @@ suppress default semantics which affect filesystem access.
 .It Dv MNT_RDONLY
 The filesystem should be treated as read-only;
 Even the super-user may not write on it.
+Specifying MNT_UPDATE withut this option will upgrade 
+a read-only filesystem to read/write.
 .It Dv MNT_NOEXEC
 Do not allow files to be executed from the filesystem.
 .It Dv MNT_NOSUID
@@ -91,9 +93,6 @@ Do not interpret special files on the filesystem.
 All I/O to the filesystem should be done synchronously.
 .It Dv MNT_ASYNC
 All I/O to the filesystem should be done asynchronously.
-.It Dv MNT_WANTRDWR
-Upgrade a mounted read-only filesystem to read-write if MNT_UPDATE
-is also specified.
 .It Dv MNT_FORCE
 Fore a read-write mount even if the filesystem appears to be unclean.
 Dangerous.