From: AITGW::"tron!clevax.dnet!jon@uunet.UU.NET" "Jon Pinkley, Westinghouse 2166" 5-FEB-1992 01:25:41.55 To: "everhart@arisia.dnet.ge.com"@uunet.UU.NET CC: Subj: Generic unix file server; Possible DECUS tape material Received: by AITGW.DECnet (utk-mail11 v1.5) ; Wed, 5 Feb 92 01:25:02 EST Received: from relay2.UU.NET by aitgw.ge.com (5.65/GE Gateway 1.4) id AA23486; Wed, 5 Feb 92 01:24:50 -0500 Received: from uunet.uu.net (via LOCALHOST.UU.NET) by relay2.UU.NET with SMTP (5.61/UUNET-internet-primary) id AA08715; Wed, 5 Feb 92 01:22:35 -0500 Message-Id: <9202050622.AA08715@relay2.UU.NET> Received: from tron.UUCP by uunet.uu.net with UUCP/RMAIL (queueing-rmail) id 012119.2961; Wed, 5 Feb 1992 01:21:19 EST Date: Wed, 5 Feb 92 01:13:07 -0500 From: tron!clevax.dnet!jon@uunet.UU.NET (Jon Pinkley, Westinghouse (216)486-8300 x1335) To: "everhart@arisia.dnet.ge.com"@uunet.UU.NET Subject: Generic unix file server; Possible DECUS tape material From: TRON::"uunet!MIAMIU.BITNET!LANWORKS" 15-JAN-1992 09:56:16.66 To: Multiple recipients of list LANWORKS CC: Subj: generic file server availability (announcement) This is a note to announce the availability of version 1.0 of the generic unix file server via ftp. The source is available via anonymous ftp from yaouk.anu.edu.au in the pub/nbserver directory. All updates will be put here in future. If you don't have anon ftp access send me some mail and I should get around to mailing it to you. There have been several changes since version 0.5 which I announced previously. In particular note the changed SERVICES file format. Have a look at the release_notes file for further details. The README file follows: ********************************************************************** Welcome to version 1.0 of a Unix file server for Dos Pathworks. (I haven't thought of a catchy name yet) This software was written to allow users of Pathworks to access file services from non-DEC machines. In doing so I did not realise that I had in fact implemented the netbios protocol. This means that (in theory at least) this software could be used with other PC clients, not just the Pathworks for DOS client. The software should work with either Decnet or TCP/IP. I have only tested it with TCP/IP. This package offers some advantages over the DEC product in that it has flags in the services file which can disable/enable guest connections, and enable/disa ble the /setdir switch (for changing the root of the connection) and enable/disable writing to the service. The software is still being enhanced, so you will probably see more versions in the near future. I have listed some known bugs at the end of this file, if you want to help fix them then please do and send me the changes for incorporation in the next release. Please report any problems with this software to Andrew Tridgell, at the email address "Andrew.Tridgell@anu.edu.au". I don't guarantee to fix the problem but I'll try my best. Also as I got a big response from the vmsnet.networks.desktop.pathworks news group perhaps some of the problems could be discussed there. Use this software at your own risk. No responsability is taken by the author for any problems caused by this software. Installation: ============= Step 1: Unpack the software into some appropriate directory on the server. Something like /usr/local/pcsa would be typical. Step 2: Edit the file "local.h" to define local preferences. At the top you should put a define for the architecture you are compiling on. Currently the ones recognised are #define SUN /* for a sun sparcstation */ or #define ULTRIX /* for a decstation */ or #define AIX /* for a rs6000 */ or #define SGI /* for a silicon graphics box */ or #define SEQUENT /* for a sequent symmetry running dynix */ Also make sure you edit the defines for PCSAIN, PCSAOUT, DEBUGFILE. These should be filenames in some appropriate directory where you want debug information to be held. If DEBUGLEVEL is 0 then they will never be used. If DEBUGLEVEL is 1 then DEBUGFILE will contain various status messages. If DEBUGLEVEL is 2 then DEBUGFILE will contain more verbose status messages. If DEBUGLEVEL is 3 then a complete binary record of all transactions between the client and server are kept in PCSAIN and PCSAOUT. The file pointed to by SERVICES should contain a pure ascii list of the file services you want available and the paths to the services. It is NOT in the same format as the DEC service.db. The format will be explained more below. The GUEST_ACCOUNT macro should point to the default account for the server. This plays the same role as the pcguest account for the dec server. If you choose to create this account note that a valid password for the account is not required. Also note that guest access can be disabled for some or all of the services in the SERVICES file. The PWDAUTH macro should be defined if your system supports the pwdauth(user,password) call. Try "man pwdauth" to see if you have it. If the compiler complains that it can't find _pwdauth then undef this #define. Step 3: Compile the code. This should require just a command like: "cc -o server server.c" If the compilation produces errors then fix them! I have compiled without errors on the architectures listed above. Step 4: Create (or just edit) the SERVICES file you defined above. The file consists of an ascii file containing three columns separated by spaces or tabs. The first column gives a service name (such as pccommon) and the second gives a path to the place where the files will be stored for this service (such as /usr/local/pccommon ). The third column (which is optional) contains flags. A 'W' flag means the service can be written to. A 'S' flag means that the /setdir function is allowed on this service. (not including this would prevent people attaching to directories other than the specified directory). A 'G' flag means that guest connections are allowed. Lines beginning with a # are assumed to be comments and will be ignored