home(8) [plan9 man page]
HOME(8) System Manager's Manual HOME(8) NAME
home, 40meg, 80meg, personalize, update, Disclabel - administration for local file systems SYNOPSIS
gnot/home gnot/personalize gnot/update magnum/home magnum/personalize magnum/update pc/40meg pc/80meg pc/personalize pc/update nextstation/home nextstation/update DESCRIPTION
These programs help maintain a file system on a local disk for a private machine. Home partitions a disk, copies the appropriate kernel to the disk, and makes a new file system on the disk. To do this, it overwrites the vendor-supplied software on the disk with a copy of Plan 9. 40meg, 80meg, and 100meg configure disks and make file systems for disks of the appropriate size. Update copies the current kernel to the disk and updates files on the local file system. It only updates those files put there by the home program. Personalize removes the contents of the /usr directory on the local disk and copies a minimal set of files for the user who runs the com- mand. The file /rc/bin/nextstation/Disclabel, despite its name, is not an rc(1) script. It contains the second stage bootstrap program for Nextstations booting from local disk. Before booting a Plan 9 Nextstation from disk, it should be installed in the partition /dev/hd1label; this is normally done by nexstation/home. FILES
/lib/proto/portproto Mkfs prototype files for magnum/home, magnum/update, gnot/home, and gnot/update. /lib/proto/386proto Mkfs prototype files for pc/40meg, pc/80meg, and pc/update. SOURCE
/rc/bin/gnot/* /rc/bin/magnum/* /rc/bin/pc/* /rc/bin/nextstation/* SEE ALSO
kfs(4), mkfs(8), prep(8), wren(3) ``Installing the Plan 9 Distribution''. HOME(8)
Check Out this Related Man Page
MKFS(8) System Manager's Manual MKFS(8) NAME
mkfs, mkext - archive or update a file system SYNOPSIS
disk/mkfs [-aprv] [-n name] [-s source] [-u users] [-z n] proto ... disk/mkext [-d name] [-u] [-h] [-v] file ... DESCRIPTION
Mkfs copies files from the file tree source (default /) to a kfs file system (see kfs(4)). The kfs service is mounted on /n/kfs, and /adm/users is copied to /n/kfs/adm/users. The proto files are read, and any files specified in them that are out of date are copied to /n/kfs. Each line of the proto file specifies a file to copy. Indentation is significant, with each level of indentation corresponding to a level in the file tree. Fields within a line are separated by white space. The first field is the last path element in the destination file tree. The second field specifies the permissions. The third field is the owner of the file, and the fourth is the group owning the file. The fifth field is the name of the file from which to copy; this file is read from the current name space, not the source file tree. All fields except the first are optional. Names beginning with a are expanded as environment variables. If the first file specified in a directory is all of the files in that directory are copied. If the first file is all of the files are copied, and all subdirectories are recursively copied. Mkfs copies only those files that are out of date. Such a file is first copied into a temporary file in the appropriate destination direc- tory 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: a Instead of writing to a kfs file system, write an archive file to standard output, suitable for mkext. All files in proto, not just those out of date, are archived. n name Use kfs.name as the name of the kfs service (default kfs). p Update the permissions of a file even if it is up to date. r Copy all files. s source Copy from files rooted at the tree source. u users Copy file users into /adm/users in the new system. v Print the names of all of the files as they are copied. z n Copy files assuming kfs block n (default 1024) bytes long. If a block contains only 0-valued bytes, it is not copied. Mkext unpacks archive files made by the -a option of mkfs. The -d option specifies a directory (default /n/kfs) to serve as the root of the unpacked file system. The -u option, to be used only when initializing a new fs(4) file system, sets the owners of the files created to correspond to those in the archive and restores the modification times of the files. (This is only permitted at the initial load of the files into a file system.) Each file on the command line is unpacked in one pass through the archive. If the 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 -v option prints the names and sizes of files as they are extracted; -h prints headers for the files on standard output instead of unpacking the files. EXAMPLES
Make an archive to establish a new file system: disk/mkfs -a -u files/adm.users -s dist proto > arch Unpack that archive onto a new file system: srv il!newfs mount -c /srv/il!newfs /n/newfs disk/mkext -u -d /n/newfs < arch FILES
/lib/proto directory of prototype files. /lib/proto/portproto generic prototype file. SOURCE
/sys/src/cmd/disk/mkfs.c /sys/src/cmd/disk/mkext.c SEE ALSO
prep(8), kfscmd(8), wren(3), pip(8) MKFS(8)