Description |
spec and dir are pointers to pathnames. mflag can assume the following values: | |
|
| to describe a file system type. |
|
| to describe a block of file-system specific data of length datalen starting at the address dataptr. |
|
| if the file system is to be mounted as read-only, in which case, no further arguments are expected. |
| The argument fstyp is interpreted by If neither If Upon successful completion of | |
Return val. | 0 | upon successful completion. |
-1 | if an error occurs. | |
Errors |
| |
|
| dir is already mounted at the time of the call, or |
|
| spec, dir or datalen points outside the allocated address space of the process. |
|
| The super-block has an invalid magic number or fstyp is invalid. |
|
| Too many symbolic links were encountered in resolving dir. |
|
| |
The length of the dir argument exceeds | ||
|
| One of the named files is not recognized. |
|
| The file system state in the super-block is not FsOKAY and mflag requests write permission. |
|
| spec is not a block-special file. |
|
| A component of spec or dir is not a directory. |
|
| The special file associated with spec is not recognized. |
|
| The effective user ID is not that of a process with appropriate privileges. |
|
| spec is not local and cannot be mounted. |
|
| spec is write-protected, and mflag requests write permission. |
Notes |
As soon as a directory is mounted, it is treated as a subtree. In other words, files on the mounted file system can be accessed by processes without making allowances for the fact a mounted file system is involved. Links across file system boundaries with The interface is intended only for the | |
See also |
|