191 lines
4.4 KiB
Groff
191 lines
4.4 KiB
Groff
.TH NCPMOUNT 8 25/11/1995 ncpmount ncpmount
|
|
.SH NAME
|
|
ncpmount \- mount program for ncpfs
|
|
.SH SYNOPSIS
|
|
.B ncpmount
|
|
.B server mount-point
|
|
[
|
|
.B -h
|
|
] [
|
|
.B -n
|
|
.I
|
|
] [
|
|
.B -P
|
|
.I password
|
|
] [
|
|
.B -C
|
|
] [
|
|
.B -s
|
|
.I server name
|
|
] [
|
|
.B -c
|
|
.I client name
|
|
] [
|
|
.B -U
|
|
.I user name
|
|
] [
|
|
.B -u
|
|
.I uid
|
|
] [
|
|
.B -g
|
|
.I gid
|
|
] [
|
|
.B -f
|
|
.I file mode
|
|
] [
|
|
.B -d
|
|
.I dir mode
|
|
]
|
|
|
|
.SH DESCRIPTION
|
|
This program is an interface to the NCP filesystem.
|
|
|
|
.B ncpfs
|
|
is a filesystem which understands the NCP protocol. This is the
|
|
protocol Novell NetWare clients use to talk to NetWare servers. ncpfs
|
|
was inspired by
|
|
.B lwared,
|
|
a free NetWare emulator for Linux written by Ales Dryak. See
|
|
ftp://klokan.sh.cvut.cz/pub/linux for this very intersting program.
|
|
|
|
.SH OPTIONS
|
|
.B server
|
|
.RS 3
|
|
.B server
|
|
is the name of the server you want to use on the server.
|
|
.RE
|
|
|
|
.B mount-point
|
|
.RS 3
|
|
.B mount-point
|
|
is the directory you want to mount the filesystem over. It's the same
|
|
as in the normal mount command.
|
|
|
|
If the real uid of the caller is not root,
|
|
.B ncpmount
|
|
checks whether the user is allowed to mount a filesystem on the
|
|
mount-point. So it should be safe to make
|
|
.B ncpmount
|
|
setuid root. The filesystem stores the uid of the user who called
|
|
ncpmount. So
|
|
.B ncpumount
|
|
can check whether the caller is allowed to unmount the filesystem.
|
|
.RE
|
|
|
|
.B -h
|
|
.RS 3
|
|
.B -h
|
|
is used to print out a short help text.
|
|
.RE
|
|
|
|
.B -C
|
|
.RS 3
|
|
By default, passwords are converted to uppercase before they are sent
|
|
to the server, because most servers require this. You can turn off
|
|
this conversion by
|
|
.B -C.
|
|
.RE
|
|
|
|
.B -n
|
|
.RS 3
|
|
.B -n
|
|
should be given to mount shares which do not require a password to log in.
|
|
.RE
|
|
|
|
.B -P
|
|
.I password
|
|
.RS 3
|
|
You may want to give the password required by the server on the
|
|
command line. You should be careful to use passwords in scripts.
|
|
|
|
If neither
|
|
.B -n
|
|
nor
|
|
.B -P
|
|
are given, ncpmount prompts for a password. This makes it difficult to
|
|
use in scripts such as /etc/rc. But that's not ncpmount's fault, but a
|
|
general problem with the fact that you need a password on every
|
|
login. If anybody has a satisfying solution to this problem, please
|
|
tell me.
|
|
.RE
|
|
|
|
.B -U
|
|
.I user name
|
|
.RS 3
|
|
If the user name your NetWare administrator gave to you differs
|
|
from your unix user-id, you should use
|
|
.B -U
|
|
to tell the server about you NetWare user name.
|
|
.RE
|
|
|
|
.B -u
|
|
.I uid,
|
|
.B -g
|
|
.I gid
|
|
.RS 3
|
|
Currently I did not implement a mapping from NetWare users/groups to
|
|
unix users/groups. Unix requires that each file has an owner
|
|
and a group it belongs to. With
|
|
.B -u
|
|
and
|
|
.B -g
|
|
you can tell ncpmount 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 cover deficiencies in the
|
|
implementation of ncpfs. I did not implement a scheme to map NetWare
|
|
permissions to unix permissions. So ncpmount 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 NOTES
|
|
If you have difficulties in mounting, please make sure that you have configured your ipx subsystem correctly. It is especially important that there is a route to the internal network of your server.
|
|
|
|
.SH ENVIRONMENT VARIABLES
|
|
.B USER / LOGNAME
|
|
.RS 3
|
|
The variables USER or LOGNAME may contain the username of the person
|
|
using the client. USER is tried first. If it's emtpy, LOGNAME is
|
|
tried.
|
|
.RE
|
|
|
|
.SH DIAGNOSTICS
|
|
|
|
Most diagnostics issued by ncpfs are logged by syslogd. Normally
|
|
nothing is printed, only error situations are logged there.
|
|
|
|
.SH SEE ALSO
|
|
.B syslogd(8), ncpumount(8)
|
|
|
|
.SH CREDITS
|
|
ncpfs would not have been possible without lwared, written by Ales
|
|
Dryak (A.Dryak@sh.cvut.cz).
|
|
|
|
The encryption code was taken from Dr. Dobbs's Journal 11/93. There
|
|
Pawel Szczerbina described it in an article on NCP.
|
|
|
|
The ncpfs code was initially hacked from smbfs by Volker Lendecke
|
|
(lendecke@namu01.gwdg.de). smbfs was put together by Paal-Kr. Engstad
|
|
(pke@engstad.ingok.hitos.no) and later polished by Volker.
|