Prerequisite: The VOB being activated must already have a VOB tag for your host's network region in the ClearCase registry. See the mkvob and mktag reference pages.
The mount command activates one or more VOBs on the local host. The mount command mounts a VOB as a file system of type MVFS (multiversion file system) and is inapplicable to non-MVFS installations.
The mount –all command mounts all public VOBs listed for your host's network region in the VOB registry. (It does not mount private VOBs or VOBs whose tag entries include the mount option noauto.) On UNIX and Linux systems, this command executes at ClearCase startup time; see the init_ccase reference page.
A public VOB can be activated by any user; if the mount-over directory does not already exist, it is created.
A private VOB can be activated only by its owner. The root user or VOB owner can use the standard mount(1M) command to mount a private VOB; other users cannot mount it. The mount-over directory must already exist and be owned by the VOB owner.
All platforms: ro, rw, soft, hard, intr, nointr, timeo, retrans, noauto, nodnlc, noac, acdirmin, acdirmax, acregmin, acregmax, actimeo
UNIX and Linux: nodev, nosuid, suid
Windows: suid (applicable only for a tag used to mount a VOB on UNIX or Linux), poolmap
The UNIX system and Linux examples in this section are written for use in csh. If you use another shell, you may need to use different quoting and escaping conventions.
The Windows examples that include wildcards or quoting are written for use in cleartool interactive mode. If you use cleartool single-command mode, you may need to change the wildcards and quoting to make your command interpreter process the command appropriately.
In cleartool single-command mode, cmd-context represents the UNIX system and Linux shells or Windows command interpreter prompt, followed by the cleartool command. In cleartool interactive mode, cmd-context represents the interactive cleartool prompt.