From c1e3c82572f880584c99fbe75082f7db2c3c7279 Mon Sep 17 00:00:00 2001 From: jkh Date: Tue, 22 Dec 1998 11:52:10 +0000 Subject: 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." --- sbin/mount_umapfs/mount_umapfs.8 | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to 'sbin/mount_umapfs/mount_umapfs.8') diff --git a/sbin/mount_umapfs/mount_umapfs.8 b/sbin/mount_umapfs/mount_umapfs.8 index 4b9bd00..1407305 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 -- cgit v1.1