This commit is contained in:
Philippe Charnier 1998-07-06 07:17:27 +00:00
parent 46fc8f78df
commit 7b353f1aca
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=37428
4 changed files with 22 additions and 18 deletions

View File

@ -35,7 +35,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_null.8 8.6 (Berkeley) 5/1/95
.\" $Id: mount_null.8,v 1.7 1997/02/22 14:32:50 peter Exp $
.\" $Id: mount_null.8,v 1.8 1997/03/11 12:33:34 peter Exp $
.\"
.Dd May 1, 1995
.Dt MOUNT_NULL 8
@ -51,7 +51,7 @@ demonstrate the use of a null file system layer
.Ar mount-point
.Sh DESCRIPTION
The
.Nm mount_null
.Nm
command creates a
null layer, duplicating a sub-tree of the file system
name space under another part of the global file system namespace.
@ -68,7 +68,7 @@ A different device number for the virtual copy is returned by
but in other respects it is indistinguishable from the original.
.Pp
The
.Nm mount_null
.Nm
filesystem differs from a traditional
loopback file system in two respects: it is implemented using
a stackable layers techniques, and it's
@ -189,7 +189,9 @@ process when constructing other vnode stacks.
.Sh CREATING OTHER FILE SYSTEM LAYERS
One of the easiest ways to construct new file system layers is to make
a copy of the null layer, rename all files and variables, and
then begin modifying the copy. Sed can be used to easily rename
then begin modifying the copy.
.Xr Sed 1
can be used to easily rename
all variables.
.Pp
The umap layer is an example of a layer descended from the
@ -228,6 +230,6 @@ UCLA Technical Report CSD-910056,
.Em "Stackable Layers: an Architecture for File System Development" .
.Sh HISTORY
The
.Nm mount_null
.Nm
utility first appeared in
.Bx 4.4 .

View File

@ -35,17 +35,17 @@
*/
#ifndef lint
char copyright[] =
static const char copyright[] =
"@(#) Copyright (c) 1992, 1993, 1994\n\
The Regents of the University of California. All rights reserved.\n";
#endif /* not lint */
#ifndef lint
/*
#if 0
static char sccsid[] = "@(#)mount_null.c 8.6 (Berkeley) 4/26/95";
*/
#endif
static const char rcsid[] =
"$Id: mount_null.c,v 1.9 1997/03/29 03:32:42 imp Exp $";
"$Id$";
#endif /* not lint */
#include <sys/param.h>

View File

@ -35,7 +35,7 @@
.\" SUCH DAMAGE.
.\"
.\" @(#)mount_null.8 8.6 (Berkeley) 5/1/95
.\" $Id: mount_null.8,v 1.7 1997/02/22 14:32:50 peter Exp $
.\" $Id: mount_null.8,v 1.8 1997/03/11 12:33:34 peter Exp $
.\"
.Dd May 1, 1995
.Dt MOUNT_NULL 8
@ -51,7 +51,7 @@ demonstrate the use of a null file system layer
.Ar mount-point
.Sh DESCRIPTION
The
.Nm mount_null
.Nm
command creates a
null layer, duplicating a sub-tree of the file system
name space under another part of the global file system namespace.
@ -68,7 +68,7 @@ A different device number for the virtual copy is returned by
but in other respects it is indistinguishable from the original.
.Pp
The
.Nm mount_null
.Nm
filesystem differs from a traditional
loopback file system in two respects: it is implemented using
a stackable layers techniques, and it's
@ -189,7 +189,9 @@ process when constructing other vnode stacks.
.Sh CREATING OTHER FILE SYSTEM LAYERS
One of the easiest ways to construct new file system layers is to make
a copy of the null layer, rename all files and variables, and
then begin modifying the copy. Sed can be used to easily rename
then begin modifying the copy.
.Xr Sed 1
can be used to easily rename
all variables.
.Pp
The umap layer is an example of a layer descended from the
@ -228,6 +230,6 @@ UCLA Technical Report CSD-910056,
.Em "Stackable Layers: an Architecture for File System Development" .
.Sh HISTORY
The
.Nm mount_null
.Nm
utility first appeared in
.Bx 4.4 .

View File

@ -35,17 +35,17 @@
*/
#ifndef lint
char copyright[] =
static const char copyright[] =
"@(#) Copyright (c) 1992, 1993, 1994\n\
The Regents of the University of California. All rights reserved.\n";
#endif /* not lint */
#ifndef lint
/*
#if 0
static char sccsid[] = "@(#)mount_null.c 8.6 (Berkeley) 4/26/95";
*/
#endif
static const char rcsid[] =
"$Id: mount_null.c,v 1.9 1997/03/29 03:32:42 imp Exp $";
"$Id$";
#endif /* not lint */
#include <sys/param.h>