Adding and removing mount configuration
Once a filesystem has been created (on the hard disk, floppy disk,
or CD-ROM) or exported from a remote server,
you must add the mount information to the system
so that you can then mount and use the filesystem.
To add filesystem mount information,
in the
Filesystem Manager:
-
Select Add Mount Configuration
from the Mount menu, then select Local
or Remote.
-
Select the appropriate filesystem:
Local-
Select the filesystem device file from the pop-up list on the local system.
If the device file does not appear in the list,
enter the correct device in the ``Device File'' field.
Remote-
Select the type of remote filesystem,
select the server from the list of hosts known to the local system,
then select the directory or volume.
-
Specify the filesystem parameters.
See
``Modifying filesystem mount configuration''.
This adds the filesystem mount configuration to the
/etc/default/filesys file and adds the filesystem
to the Filesystem Manager list.
NOTE:
Remote administration (using the Open Host selection of
the Host menu) requires user equivalence on the machine
you plan to administer. The remote machine must recognize the
account being used to administer users on the local machine. See
``Adding user equivalence''
for more information. As on the local machine, non-root
accounts require the sysadmin authorization to run the
Filesystem Manager. See
``Assigning subsystem authorizations''
for more information.
If you selected ``Now'' to mount the filesystem immediately,
the Mount icon appears to the left of the filesystem name
indicating that the filesystem is mounted.
To remove the mount configuration for a filesystem,
select Remove Mount Configuration
from the Mount menu and click on Yes
at the prompt.
This removes the mount information from the /etc/default/filesys
file and the filesystem no longer appears in the
Filesystem Manager list.
If the filesystem is mounted, removing the mount configuration
also unmounts the filesystem.
Next topic:
Modifying filesystem mount configuration
Previous topic:
Allocating additional server lockd daemons
© 2005 The SCO Group, Inc. All rights reserved.
SCO OpenServer Release 6.0.0 -- 02 June 2005