From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.protocols.nfs
Subject: Re: PC-NFS printing
Date: 8 Oct 92 12:48:12 GMT
Organization: SunSelect
NNTP-Posting-Host: tyger.east.sun.com

Quoth pgreen@zia.aoc.nrao.edu (Philip Green) (in <1992Oct7.174001.7703@zia.aoc.nrao.edu>):
#I am having problems with printing;
#
#Server: Solbourne 
#PC-NFS:4.0
#
#net use LPT1: server:printername
#
#returns
#
#NFS230F: There is no printer named printername on server
#
#The printer does exist and works fine for all the Sparcs.
#
#When I used net printers server I got a list of printers
#but with the second name from the printcap file. I then
#tried
#
#net use LPT1: server:printername(the one returned by net printers)
#
#This time the return was
#
#NFS040F: The specified file system is not local to server
#
#
#What do I have to do to make this work?
#
#-- 
#Phil Green                           	pgreen@aoc.nrao.edu
#NRAO					505.835.7294

(1) To get around the "second name" problem, pick up the latest pcnfsd
from bcm.tmc.edu and configure it to use only BSD-style commands.
(The problem lies with the SunOS 4.x implementation of lpstat.)

(2) To get around the second problem, make sure that the spool
directory (by default /usr/spool/pcnfs) is exported without
any restrictions. Check the man page for pcnfsd for details
on how to change the default spool directory.

While on this topic, let me include something I just posted to
the BSD/386 beta mailing list:

#From geoff Thu Oct  8 08:35:12 1992
#Subject: Re: pcnfs
#
#>> From: dougc@htbawd.rain.com (Doug Carter)
#>> Subject: pcnfs
#>> 
#>> 
#>> Is there anyone out there running pcnfs (from a PC-DOS machine) to
#>> a BSDI server? Even though I've exported a filesystem to everybody,
#>> pcnfs still gets access denied when trying to mount it.
#>> 
#>> Do I need pcnfsd running on the BSDI machine before this will work?
#
#No, though it's easy to install (use the BSD version on bcm.tmc.edu).
#
#The restriction here is that you can only mount the export point
#*exactly* - not a subdirectory of the export point. This means that
#setting up printing is a bit messy: suppose you have four PC-NFS
#clients named alpha, beta, gamma and delta, and you want to use
#/usr/spool/pcnfs as the PC-NFS printing spool directory. Recall that
#the default behaviour of pcnfsd is to create a subdirectory with the
#same name as the PC client and pass the path to this directory back
#to the PC, which mounts it and writes print files therein. Well, in
#BSD/386 (or any NFS derived from the University of Guelph implementation),
#you must explicitly export every directory which might be mounted, i.e.:
#
#        /usr/spool/pcnfs/alpha
#        /usr/spool/pcnfs/beta
#        /usr/spool/pcnfs/gamma
#        /usr/spool/pcnfs/delta
#
#I'm not sure why the Guelph U. NFS code doesn't include the logic
#to march back up the requested mount path until it matches an
#export point (stat'ing each directory along the way to make sure
#you don't cross another mount point). It shouldn't be hard to 
#incorporate. [Unfortunately I don't think I can provide the code, since
#I work with the Sun NFS source on a regular basis, and I don't want any
#risk of "taint".] Does anyone know if OSF did this when they folded
#the same code base into OSF/1?
#
#Geoff
--
Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
-----------
News software that enforces a four-line .signature limit is responsible for
the fact that these postings just go on and on and on and seem to end in mid-
Newsgroups: comp.protocols.nfs