3 mount, umount \- mount or umount a file system
9 int mount(char *\fIspecial\fP, char *\fIname\fP, int \fImountflags\fP, char *\fItype\fP, char *\fIargs\fP)
10 int umount(char *\fIname\fP)
11 int umount2(char *\fIname\fP, int \fIflags)
16 tells the system that the file system
18 is to be mounted on the file
20 effectively overlaying
25 may of any type, except that if the root of
29 must also be a directory.
31 must be a block special file, or a NULL pointer.
32 If a NULL pointer is passed, the file system is
33 mounted without a block device.
35 may be a bitwise combination of the following flags:
38 Mount file system read-only, rather than read-write.
41 Reuse the file system server image if possible.
44 Do not start the file system server, but use existing one. The label of
45 the running file server is specified in
49 is the type of the file system (e.g. "mfs"), used to pick a file system server.
50 If this parameter is NULL, the default type is used.
52 is a string with arguments passed to the file system server.
53 Their interpretation is up to the server.
54 This parameter may be NULL as well.
57 removes the connection between a device and a mount point,
59 may refer to either of them. If more than one device is mounted on the
60 same mount point then unmounting at the mount point removes the last mounted
61 device, unmounting a device removes precisely that device. The unmount will
62 only succeed if none of the files on the device are in use.
65 Same as Umount(), but takes an additional
69 may be a bitwise combination of the following flags:
72 Umount the file system but do not terminate the the file system server.
75 These calls may only be executed by the super-user.
80 Kees J. Bot (kjb@cs.vu.nl)