Copyright (c) 2009, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
See the License for the specific language governing permissions and limitations under the License. When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with
the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
The smbfs file system allows you to mount CIFS shares that are exported from Windows or compatible systems. SMB is the historical name for the CIFS protocol, which stands for Server Message Block and is more commonly used in technical contexts.
The smbfs file system permits ordinary UNIX applications to change directory into an smbfs mount and perform simple file and directory operations. Supported operations include open, close, read, write, rename, delete, mkdir, rmdir and ls.
Some local UNIX file systems (for example UFS) have features that are not supported by smbfs. These include:
No mapped-file access because mmap(2) returns ENOSYS.
Locking is local only and is not sent to the server.
The following are limitations in the CIFS protocol:
unlink() or rename() of open files returns EBUSY.
rename() of extended attribute files returns EINVAL.
Creation of files with any of the following illegal characters returns EINVAL: colon (:), backslash (\\), slash (/), asterisk (*), question mark (?), double quote ("), less than (<), greater than (>), and vertical bar (|).
chmod and chown settings are silently discarded.
Links are not supported.
Symbolic links are not supported.
mknod is not supported. (Only file and directory objects are supported.)
The current smbfs implementation does not support multi-user mounts. Instead, each Unix user needs to make their own private mount points.
Currently, all access through an smbfs mount point uses the Windows credentials established by the user that ran the mount command. Normally, permissions on smbfs mount points should be 0700 to prevent Unix users from using each others' Windows credentials. See the dirperms option to mount_smbfs(1M) for details regarding how to control smbfs mount point permissions.
An important implication of this limitation is that system-wide mounts, such as those made using /etc/vfstab or automount maps are only useful in cases where access control is not a concern, such as for public read-only resources.
See attributes(5) for descriptions of the following attributes:
| ATTRIBUTE TYPE ATTRIBUTE VALUE |
| Interface Stability Uncommitted |
smbutil(1), mount_smbfs(1M), nsmbrc(4), attributes(5)