| MKFS(8) | System Manager's Manual | MKFS(8) |
mkfs, mkext - archive or update a file system
disk/mkfs [-aprvxS] [-d dest] [-n name] [-s source] [-u users] [-z n] [-G group] [-U user] proto ...
disk/mkext [-d name] [-f] [-h] [-T] [-u] [-v] [ file ... ]
Mkfs copies files from the file tree source (default /) to a kfs file system (see kfs (4)) assumed to be mounted on dest (default: /n/kfs). The proto files are read, and any files specified in them that are out of date are copied to dest. See proto (6) for the description of file system prototype files.
Mkfs by default copies only those files that are out of date. Such a file is first copied into a temporary file in the appropriate destination directory and then moved to the destination file. Files in the kfs file system that are not specified in the proto file are not updated and not removed.
The options to mkfs are:
Mkext unpacks an archive created by the -a option of mkfs, read from the standard input. If one or more files are specified on the command line, only those files are unpacked. If a file is a directory, all files and subdirectories of that directory are also unpacked. When a file is unpacked, the entire path is created if it does not exist. If no files are specified, the entire archive is unpacked; in this case, missing intermediate directories are not created. The options are:
Make an archive to establish a new file system (assuming that the output file arch is not referenced by proto):
bind '#U' /n/local
disk/mkfs -a -s /n/local proto > arch
Unpack that archive on another machine:
mount tcp!server /n/remote
disk/mkext -u -d /n/remote < arch
/appl/cmd/disk/mkfs.b
/appl/cmd/disk/mkext.b