A SAMBA V1.9.16alpha8-VMS1 for OpenVMS	 (VAX and Alpha)	14-Jul-1996   0 	Ported by Eckart Meyer <meyer@ifn.ing.tu-bs.de>  9 ========================= CAUTION ======================= 4 This software is alpha test. It has not been wideley8 tested until now. It currently runs ONLY with UCX. Other7 packages will be supported later by a future version of 8 SOCKETSHR. The current version of SOCKETSHR (V0.9D) does3 not support the needed server socket function nor a  working setsockopt() function.  + Current restrictions: Tested only on Alpha. 0 Will compile only with DEC-C Version 4 or later.$ NOTE: NMBD DOES NOT WORK SO FAR!!!!!9 =========================================================    WHY SAMBA FOR VMS   7 	There is Digital's Pathworks. It's not that expensive. - 	Cost was not the reason to get SAMBA on VMS. 9 	In short, SAMBA has what is missing in Pathworks for VMS 5 	V4 and it is easier to handle than Pathworks for VMS ) 	V5. So it's somewhere between V4 and V5.   ' 	Advantages of SAMBA over Pathworks V4:    	- Implements LANmanager V2.& 	- Long filenames for Win95 and WinNT.F 	- Same LANmanager implementation on all hosts in a mixed environment." 	- Public domain, no license cost.  ' 	Advantages of SAMBA over Pathworks V5:   2 	- Uses VMS security instead of it's own like PW5.: 	- Less resources (well, if lots of clients are connected,' 	  SAMBA creates lots of processes...).  	- Easier to manage.F 	- Same LANmanager implementation on all hosts in a mixed environment." 	- Public domain, no license cost.   	Disadvantages:   / 	- May be slower (not really tested until now). & 	- TCP/IP only. No DECnet, no NETBEUI.4 	- Can't be primary domain controller (still true??)) 	- Public domain, no guarranteed support.  	- I'm sure, there are more...   BUILDING FROM SOURCES   2 	Extract the files and go to the SOURCE directory." 	If you don't have MMS or MMK type  9 	$ @[.VMS]BUILD		(to rebuild all files: @[.VMS]BUILD ALL)   : 	If MMS or MMK is present (I have MMK, MMS is not tested):   	$ @[.VMS]SETUP  	$ MMS/DESCRIP=[.VMS]   6 	MMS/MMK can be used to build only part of the package3 	(e.g. MMS/DESCRIP=[.VMS] SMBD) or changed modules.    	Proceed with INSTALLATION.    USING BINARY DISTRIBUTION   2 	Executables are not provided. Extract the archive 	to a directory and type   	$ @LINK   	Proceed with INSTALLATION.    INSTALLATION  A 	What /usr/local/samba is for UNIX, that's the logical SAMBA_ROOT 3 	in VMS. The value of this logical will be asked in    	$ @[.VMS]INSTALL   D 	and then all neccesary files will be copied to that directory tree.* 	The source directory may be removed then.  - 	Edit SAMBA_ROOT:[LIB]SMB.CONF to your needs. 9 	Note that all paths must be written in UNIX syntax, i.e. ? 	DUA0:[MY.DIRECTORY]MY.FILE becomes /dua0/my/directory/my.file.   @ 	Edit SAMBA_ROOT:[BIN]NMBD_STARTUP.COM and change to your needs:   	- the Broadcast address (-B)  	- the net mask (-N) 	- the working group name (-G)  < 	Normally, broadcast address and net mask should be detected: 	automatically, but this does still not work in this port.  @ 	If you don't already have a time zone logical SYS$TIME_ZONERULE8 	(or POSIX$DEFAULT_TZ), you must do so now. See the fileE 	TIME_ZONERULE.TXT for the format of that logical. Add the definition 0 	of the logical to SYS$MANAGER:SYSTARTUP_VMS.COM: 	(or SYS$MANAGER:SYSTARTUP_V5.COM for older VMS versions).  B 	A file SYS$STARTUP:SAMBA_STARTUP.COM is generated. Executing thisA 	file defines the logical SAMBA_ROOT, starts the NMBD process and @ 	setup SMBD as an UCX service. This procedure should be includedB 	in SYS$MANAGER:SYSTARTUP_VMS.COM (or SYS$MANAGER:SYSTARTUP_V5.COM 	for older VMS versions).    PROCESSES and SECURITY  D 	SAMBA generally creates one process per session. In VMS the processE 	is created by the auxilliary server of the TCP/IP package (so called ; 	in UCX, this may differ for other packages - it's the same : 	mechanism than UNIX' inetd). Each session can handle many? 	connections and each connection can be established for another C 	user (only if samba's security setting is not 'user'). The process > 	"becomes" the process of the actual user by changing it's ownD 	username, UIC, privilege mask and identifiers. This way the processB 	has exactly the rights of the connected user. If a service allowsC 	for public access, the guest account may be used. The process name D 	is changed to reflect the (netbios-) name of the connecting client.  B 	Generally SAMBA always uses the host's security mechanisms. SAMBA/ 	does not implement it's own security checking.   
 PARAMETERS  $ 	Some recommendation for parameters:  . 	printcap name = /sys$manager/ucx$printcap.dat  . 		For UCX it's printcap file is o.k. For other2 		TCP/IP packages I don't know. If it not present, 		create one (see smb.conf).  G 	print command = print %f/queue=%p/delete/passall/name="""""%f""""" !%s   8 		Use VMS DCL PRINT command. Note that you must use "%f"1 		as the file name, %s has UNIX file spec syntax. ; 		Due to a bug (at least in 1.9.13) a print command without 5 		%s fails. As a workaround, use %s in a DCL comment.    	lprm command = delete/entry=%j   = 		You may also specify a command procedure to also delete the  		temp file.   	smbrun = smbrun 	 9 		When using the supplied SMBD_STARTUP.COM this parameter 6 		must be specified exactly as stated here. Samba uses9 		the string for testing the existance of a file and then 7 		to run it. For VMS, we define the string as a logical < 		pointing to the file and as a symbol which runs that file.   	read prediction = yes  8 		Transfer from server is slightly faster for stream and; 		fixed files. For variable record files this may slow down 5 		the transfer since the "prediction read" reads from 8 		1024 byte boundaries which causes seek calls. The seek: 		routine for record files will have to rewind and re-read 		the files.   	socket options = TCP_NODELAY   7 		If it is really used by UCX there seem no difference.    	read raw = yes   1 		Is 'yes' by default. Setting to 'no' slows down  		the transfer.    FILE FORMATS  2 	Files sent to VMS will always have STREAM format.   	When reading files from VMS:   C 	Variable Record, implied carriage return (standard VMS text file):   7 		The file is read record by record and a CR/LF pair is 8 		appended. The file appears correctly as a text file atA 		the client and is padded with zeros at the end to fill the file 6 		up to the size reported by VMS (a VAR file is always: 		bigger or same size than a Stream file). When using this< 		format, performance may be poor since file seek operations3 		may cause the file to be read from the beginning.   ; 	For all other formats the file contents is sent unchanged:    	Stream:  9 		Client's "native" format. Valid for all types of files. 1 		Textfiles have a CR/LF pair as line terminator. - 		The file's size will be reported correctly.    	Stream_Linefeed:   6 		The UNIX format. Binary files will appear correctly.8 		On text files, each line is terminated by only one LF.@ 		Some programs may work, other may not (e.g. Windows' notepad).   	Fixed:   > 		Since the file does not contain any format information, this. 		file format should be o.k. for binary files.   	Other formats:   5 		These are VMS specific and does not make much sense  		at the client.    
 FILE NAMES  A 	SAMBA for VMS does not distinguish between lower and upper case. : 	All file names are presented in lower case to the client.  G 	File names which contain characters not possible for VMS are converted C 	using the same scheme that Digital's Pathworks uses: The character = 	is converted to two underlines followed by the two character > 	hex ascii code (this means that non-ASCII letters like german) 	umlauts are NOT converted to lowercase).    PRINT QUEUES  = 	Unlike the original SAMBA for UNIX getting information about @ 	queues does not spawn a new process to execute a shell command.? 	Instead, the $GETQUI system service is used to directly obtain ; 	this information from the queue manager. Since the windows = 	print manager (when running) frequently polls the server for = 	status information, this saves much resources. Submitting to F 	a print queue is done via a subprocess executing a DCL PRINT command.A 	This way, the format of the print command can easily be modified = 	by the appropriate entries in SMB.CONF. The same is true for 
 	job removal.    BUGS  @ 	NMBD does not correctly determine its own broadcast address andE 	network mask. They must be explicitly specified in NMBD_STARTUP.COM.   ? 	File sharing requests will probably not work. Untestet so far.    	Probably many unknown bugs...  