mount_nucfs(1M)


mount_nucfs -- mount a NetWare Unix Client filesystem (nucfs)

Synopsis

mount [-F nucfs] [generic_options] [-r] [-o specific_options]
special mount_point

Description

The nucfs-specific mount command mounts the specified NetWare volume as a nucfs type filesystem under the directory specified by mount_point. The mount_point specified must already exist or an error is returned; it's name becomes the name of the root of the newly mounted filesystem.

The special parameter is a NetWare volume specification in either bindery-style or nds-style formats (bindery-style is assumed unless you specify -o nds; see the specific_options, below).

A bindery-style volume specification is in the format

server/volume:

where server is the name of the NetWare server and volume is the name of the volume on that server (followed by a colon -- for example, ``SERVER1/SYS:'') that you want to mount on UnixWare.

An NDS-style volume specification uses a fully specified or aliased NDS object name in typed or untyped format. For example, the two object names

CN=SYSVOL.OU=SALES.O=COMPANY

SYSVOL.SALES.COMPANY

refer to the same volume. The same volume could also be aliased simply as ``SYSVOL'', or any other valid NDS alias.

Since the NDS format can take so many forms, you should use the -o nds option to ensure that mount interprets special as an NDS-format name.

See the NetWare Concepts book for an explanation of NDS object names.

The generic_options (as well as other information that applies to mounted filesystems of all types) are listed on the generic mount(1M) manual page.

nucfs-specific options

-F nucfs
Specify a nucfs FSType.

-r
Mount the filesystem read-only.

-o
Specify nucfs-specific options (see below). Separate multiple options with commas.

rw | ro
Read/write or read-only. Only one can be specified. Default is rw.

suid | nosuid
Indicates whether the setuid bit on files is honored or ignored (respectively) on execution. Only one can be specified. Default is suid.

bindery | nds
Indicates whether the special is a bindery-style volume specification or an NDS-style volume specification. If neither is specified, bindery-style syntax (-o bindery) is assumed.

remount
If the special is already mounted read-only, remount it read-write.

notrunc
Do not truncate long filenames.

grpid
Create a file with its GID set to the effective GID of the calling process. This behavior may be overridden on a per-directory basis by setting the setgid bit of the parent directory; in this case, the GID is set to the GID of the parent directory (see open(2) and mkdir(2)). Files created on filesystems that are not mounted with the grpid option will obey BSD semantics; that is, the GID is unconditionally inherited from that of the parent directory.

uid=name | uid=number

gid=name | gid=number
These options specify the UnixWare user whose credentials are used during the mount. These options allow the mount command to be issued from a command shell run by root even if root has not authenticated to the server.

Files

/etc/mnttab
Table of currently mounted filesystems

Examples

To mount the volume ``docs'' on SERVER1 at mount point /nw/server1/docs as a read-only filesystem where setuid bits on files are ignored, you could enter either of the following two commands (assuming that NDS has been set up as indicated in the second command):

mount -F nucfs -o rw,nosetuid server1/docs: /nw/server1/docs

mount -F nucfs -o rw,nosetuid,nds server1_docs /nw/server1/docs

References

mnttab(4), generic mount(1M), mount(2), setmnt(1M), setuid(2)

Notices

The uid= and gid= options are used as follows:
   $ id 
   uid=6192(user1) gid=713(group1) 
   $ nwlogin server1/user1 
   $ su 
   # mount -F nucfs -o uid=6192 gid=713 server1/test1: /mnt 
   # exit 
   $ 
In the example above, the kernel uses the specified uid (6192) to locate the authenticated connection for user1. The kernel then uses this connection to communicate with the server.

This is necessary when, for example, a mount command is issued from a shell script that runs on UnixWare with the owning uid of the process set to root, and the script attempts to mount a NetWare volume on behalf of an already authenticated (or auto-authenticated) user. The uid and gid options eliminate the need for root to authenticate to the server to accomplish the mount; the user's existing connection is used.

Furthermore, if the volume to be mounted is a Unix or NetWare mode volume (i.e. not DOS mode) then the specified uid (6192) and gid (713) are sent to the server in the NetWare Core Protocol (NCP) requests issued during the mount.

Once the mount has been accomplished, the specified uid and gid are forgotten by the kernel, and thus have no lasting effects.


30 January 1998
© 1998 The Santa Cruz Operation, Inc. All rights reserved.