|
|
Rocks clusters make sense for educational environments
|
|
dmu(8) System Manager's Manual dmu(8) NAME
dmu - Dataless management utility SYNOPSIS
/usr/sbin/dmu DESCRIPTION
The dataless management utility (dmu) manages Dataless Management Services (DMS) environments and clients, letting you install, configure, and list DMS environments, and add, list, modify, or remove DMS clients. DMS maintains root (/), /usr, and /var file systems on a DMS server for DMS clients. All swapping and dumping is done on the DMS client's local disk. The dmu utility creates a root file system based on the software subsets installed in the DMS environment area on the server. This root file system is accessed by DMS clients over a Local Area Network (LAN). DMS lets system administrators customize the root file systems before it is accessed by DMS clients. Caution DMS is not supported in a clusters environment. A cluster member cannot be a DMS server or a dataless client. Dataless Management Services The DMS server maintains a separate copy of the root file system for each DMS client in a client root directory (usually /clients) in the DMS area. Each DMS root area is customized for the DMS client to allow for different environmental requirements. The DMS server also reserves a DMS area where copies of the /usr file system reside. The /usr file system is shared by DMS clients with read-only access. The server's DMS root and /usr areas are available to DMS clients through a network file system (NFS), with each client accessing the DMS disk area on the DMS server over a LAN. Each DMS client is booted over the network from its private root area on the DMS server. Once booted, the DMS client continues to use its root files and /usr files from the server's DMS area. DMS Environments One or more DMS environments can reside in a DMS area. Each DMS environment contains one or more root areas; a root area exists for each general type of DMS client supported. DMS client root areas reside in the /var/adm/dms directory, and are named /var/adm/dms/dmsN.arch, where N is a sequentially-assigned integer starting with 0 and arch is a name identifying the client's machine architecture, such as alpha. The first DMS area for Alpha clients would be named /var/adm/dms/dms0.alpha. DMS Client Areas DMS maintains a DMS client area in the /clients directory. Each root area for an individual DMS client is tailored from the appropriate generic root file system, and contains a customized kernel to support that DMS client's actual system configuration. Each DMS client views its private root area and the shared /usr area as local although these areas actually reside on the DMS server and are accessed through NFS. As with the /var/adm/dms area, multiple client areas can be established in different partitions. DMS Software Installation Use the dmu utility's Install Software option to install software into each /var/adm/dms/dmsN.arch file system. All software must be installed and configured in the DMS server area before DMS clients can be added to the DMS environment. DMS Client Registration Before you use the dmu utility to serve a DMS client, you must register the DMS client for a DMS area or make an entry for the DMS client in the /etc/hosts file on the DMS server. You must have the following information to register a DMS client: The client's host name. The /var/adm/dms/dmsN.arch DMS environment where the DMS client will be registered. The location of the DMS client's root directory. The path must not exceed 25 characters and be located under the /clients directory. The DMS client's network interface, subnet mask, and default route for this network interface. The DMS client's hardware network address. The gateway address between the DMS client and server. The swap device and partition and swap device type. The type of kernel build support to be provided for the DMS client. RESTRICTIONS
You must log in as root or have superuser privileges to invoke the dmu utility. Tru64 UNIX DMS servers do not support dataless environments on DMS clients that do not support the BOOTP Internet Boot Protocol. DMS is not supported in a clusters environment. A cluster member cannot be a DMS server or a dataless client. EXAMPLES
The following command invokes the dmu utility from the root system prompt on the DMS server: # /usr/sbin/dmu You see the DMU Main Menu, and you can select dmu functions. *** DMU Main Menu *** Choices without key letters are not available. a) ADD a client c) CONFIGURE software environments d) DELETE software environments i) INSTALL software environments l) LIST registered clients m) MODIFY a client r) REMOVE a client s) SHOW software environments x) EXIT Enter your choice: Available menu options depend upon previous actions. For example, you cannot list, modify, or remove clients until you have added at least one DMS client. In that case, the m, l, and r key letters are not shown in front of their respective options: a) ADD a client c) CONFIGURE software environments d) DELETE software environments i) INSTALL software environments ) LIST registered clients ) MODIFY a client ) REMOVE a client s) SHOW software environments x) EXIT FILES
Base directory for Dataless Management Services Default location of client's root directory DMS client database file SEE ALSO
Commands: bindsetup(8), doconfig(8), nissetup(8), pmerge(8), setld(8) Files: bootptab(4) Sharing Software on a Local Area Network Installation Guide Installation Guide -- Advanced Topics dmu(8)
