d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

User reports that using mount_null destroyed his filesystem, I reply

Browse Source 
that nullfs really doesn't work, he askes why this isn't noted for the
"dangerous" filesystems, I go "hmmm."
This commit is contained in:
Jordan K. Hubbard 1998-12-22 11:52:10 +00:00
parent cf9443f92b
commit 558408f95d
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=42003
6 changed files with 66 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
sbin/mount_null/mount_null.8
View File

@ -35,7 +35,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_null.8 8.6 (Berkeley) 5/1/95
.\" $Id: mount_null.8,v 1.8 1997/03/11 12:33:34 peter Exp $
.\" $Id: mount_null.8,v 1.9 1998/07/06 07:17:26 charnier Exp $
.\"
.Dd May 1, 1995
.Dt MOUNT_NULL 8
@ -228,6 +228,16 @@ is that vnodes arguments must be manually mapped.
.sp
UCLA Technical Report CSD-910056,
.Em "Stackable Layers: an Architecture for File System Development" .
.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

12
sbin/mount_nullfs/mount_nullfs.8
View File

@ -35,7 +35,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_null.8 8.6 (Berkeley) 5/1/95
.\" $Id: mount_null.8,v 1.8 1997/03/11 12:33:34 peter Exp $
.\" $Id: mount_null.8,v 1.9 1998/07/06 07:17:26 charnier Exp $
.\"
.Dd May 1, 1995
.Dt MOUNT_NULL 8
@ -228,6 +228,16 @@ is that vnodes arguments must be manually mapped.
.sp
UCLA Technical Report CSD-910056,
.Em "Stackable Layers: an Architecture for File System Development" .
.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

12
sbin/mount_umap/mount_umap.8
View File

@ -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

12
sbin/mount_umapfs/mount_umapfs.8
View File

@ -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

12
sbin/mount_union/mount_union.8
View File

@ -33,7 +33,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_union.8 8.6 (Berkeley) 3/27/94
.\" $Id$
.\" $Id: mount_union.8,v 1.4 1998/07/15 06:13:45 charnier Exp $
.\"
.Dd March 27, 1994
.Dt MOUNT_UNION 8
@ -183,6 +183,15 @@ accessible via
.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.
Without whiteout support from the filesystem backing the upper layer,
there is no way that delete and rename operations on lower layer
objects can be done.
@ -200,3 +209,4 @@ The
.Nm
command first appeared in
.Bx 4.4 .
It first worked in FreeBSD-(fill this in).

12
sbin/mount_unionfs/mount_unionfs.8
View File

@ -33,7 +33,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_union.8 8.6 (Berkeley) 3/27/94
.\" $Id$
.\" $Id: mount_union.8,v 1.4 1998/07/15 06:13:45 charnier Exp $
.\"
.Dd March 27, 1994
.Dt MOUNT_UNION 8
@ -183,6 +183,15 @@ accessible via
.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.
Without whiteout support from the filesystem backing the upper layer,
there is no way that delete and rename operations on lower layer
objects can be done.
@ -200,3 +209,4 @@ The
.Nm
command first appeared in
.Bx 4.4 .
It first worked in FreeBSD-(fill this in).