Search all pages
Professions, Sciences, Humanities, Business, ...
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...
Conversions, tests, processing, manipulation,...
Integer, Floating point, Matrix, Statistics, Boolean, ...
Algorithms, Memory, Process control, Debugging, ...
Data storage, Integrity, Encryption, Compression, ...
Networks, protocols, Interprocess, Remote, Client Server, ...
Timing, Calendar and Clock, Audio, Video, Printer, Controls...
Management, Filtering, File & Directory access, Viewers, ...
RocketLink!--> Man page versions:
MOUNT_UMAP(8) OpenBSD System Manager's Manual MOUNT_UMAP(8)
mount_umap - sample file system layer
mount_umap [-o options] -u uid-mapfile -g gid-mapfile target mount-point
The mount_umap command is used to mount a sub-tree of an existing file
system that uses a different set of uids and gids than the local system.
Such a file system could be mounted from a remote site via NFS or it
could be a file system on removable media brought from some foreign loca-
tion that uses a different password file.
The options are as follows:
-o Options are specified with a -o flag followed by a comma separat-
ed string of options. See the mount(8) man page for possible op-
tions and their meanings.
The mount_umap command uses a set of files provided by the user to make
correspondences between uids and gids in the sub-tree's original environ-
ment and some other set of ids in the local environment. For instance,
user smith might have uid 1000 in the original environment, while having
uid 2000 in the local environment. The mount_umap command allows the
subtree from smith's original environment to be mapped in such a way that
all files with owning uid 1000 look like they are actually owned by uid
target should be the current location of the sub-tree in the local sys-
tem's name space. mount-point should be a directory where the mapped
subtree is to be placed. uid-mapfile and gid-mapfile describe the map-
pings to be made between identifiers. Briefly, the format of these files
is a count of the number of mappings on the first line, with each subse-
quent line containing a single mapping. Each of these mappings consists
of an id from the original environment and the corresponding id in the
local environment, separated by white space. uid-mapfile should contain
all uid mappings, and gid-mapfile should contain all gid mappings. Any
uids not mapped in uid-mapfile will be treated as user NOBODY, and any
gids not mapped in gid-mapfile will be treated as group NULLGROUP. At
most 64 uids can be mapped for a given subtree, and at most 16 groups can
be mapped by a given subtree.
The mapfiles can be located anywhere in the file hierarchy, but they must
be owned by root, and they must be writable only by root. mount_umap
will refuse to map the sub-tree if the ownership or permissions on these
files are improper. It will also balk if the count of mappings in the
first line of the map files is not correct.
The layer created by the mount_umap command is meant to serve as a simple
example of file system layering. It is not meant for production use.
The implementation is not very sophisticated.
The mount_umap utility first appeared in 4.4BSD.
4.4BSD March, 27, 1994 1
Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.
(Corrections, notes, and links courtesy of RocketAware.com)
FreeBSD Sources for mount_umap(8)
OpenBSD sources for mount_umap(8)
Up to: Specific Types of File Systems - Specific forms of file systems. DFS, NFS, MS-DOS, etc.
Up to: File System Operations - Operations for entire file-systems (quotas, configuration, consistency, mount, unmount, et al)
RocketLink!--> Man page versions:
Search | About | Comments | Submit Path: RocketAware > man pages >
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments