blob: 0bd87a70fc83229da38ee46f56ba4b683829d22d (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
.TH SMBMNT 8 "08 Jan 1998" "smbmnt 1.9.18"
.SH NAME
smbmnt \- mount smb file system
.SH SYNOPSIS
.B smbmnt
.B mount-point
[
.B -u
.I uid
] [
.B -g
.I gid
] [
.B -f
.I file mode
] [
.B -d
.I dir mode
]
.SH DESCRIPTION
.B smbmnt
is a little helper application for the smbmount program. smbmnt is
meant to be installed setuid root to enable normal users to mount
their smb shares. Smbmnt checks whether the user calling it has write
permissions on the mount point and then mounts the directory.
.B -u
.I uid,
.B -g
.I gid
.RS 3
A Lan Manager server does not tell us anything about the owner of a
file. Unix requires that each file has an owner and a group it belongs
to. With
.B -u
and
.B -g
you can tell smbmount which id's it should assign to the files in the
mounted direcory.
The defaults for these values are the current uid and gid.
.RE
.B -f
.I file mode,
.B -d
.I dir mode
.RS 3
Like
.B -u
and
.B -g,
these options are also used to bridge differences in concepts between
Lan Manager and unix. Lan Manager does not know anything about file
permissions. So smbmount has to be told which permissions it should
assign to the mounted files and direcories. The values have to be
given as octal numbers. The default values are taken from the current
umask, where the file mode is the current umask, and the dir mode adds
execute permissions where the file mode gives read permissions.
Note that these permissions can differ from the rights the server
gives to us. If you do not have write permissions on the server, you
can very well choose a file mode that tells that you have. This
certainly cannot override the restrictions imposed by the server.
.RE
.SH SEE ALSO
.B smbmount(8)
|
