aboutsummaryrefslogtreecommitdiff
path: root/sbin/mount_umapfs
diff options
context:
space:
mode:
authorJordan K. Hubbard <jkh@FreeBSD.org>1998-12-22 11:52:10 +0000
committerJordan K. Hubbard <jkh@FreeBSD.org>1998-12-22 11:52:10 +0000
commit558408f95d00561c18e48dd47f2b8d611af27ded (patch)
tree3af48d9a28cbf8815725841cfbb8c5b70b939a37 /sbin/mount_umapfs
parentcf9443f92bed216db1c141cba3db16c5347c69fb (diff)
downloadsrc-558408f95d00561c18e48dd47f2b8d611af27ded.tar.gz
src-558408f95d00561c18e48dd47f2b8d611af27ded.zip
User reports that using mount_null destroyed his filesystem, I reply
that nullfs really doesn't work, he askes why this isn't noted for the "dangerous" filesystems, I go "hmmm."
Notes
Notes: svn path=/head/; revision=42003
Diffstat (limited to 'sbin/mount_umapfs')
-rw-r--r--sbin/mount_umapfs/mount_umapfs.812
1 files changed, 11 insertions, 1 deletions
diff --git a/sbin/mount_umapfs/mount_umapfs.8 b/sbin/mount_umapfs/mount_umapfs.8
index 4b9bd0016be5..1407305aed31 100644
--- a/sbin/mount_umapfs/mount_umapfs.8
+++ b/sbin/mount_umapfs/mount_umapfs.8
@@ -34,7 +34,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_umap.8 8.4 (Berkeley) 5/1/95
-.\" $Id$
+.\" $Id: mount_umap.8,v 1.8 1998/07/15 06:12:31 charnier Exp $
.\"
.Dd May 1, 1995
.Dt MOUNT_UMAP 8
@@ -123,6 +123,16 @@ sophisticated.
.Sh SEE ALSO
.Xr mount 8 ,
.Xr mount_null 8
+.Sh BUGS
+
+THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK)
+AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR
+OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET.
+
+This code also needs an owner in order to be less dangerous - serious
+hackers can apply by sending mail to hackers@freebsd.org and announcing
+their intent to take it over.
+
.Sh HISTORY
The
.Nm