Xref: utzoo comp.windows.x:7176 comp.terminals:1036
Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!cornell!uw-beaver!blake!ogccse!littlei!omepd!inteloa!smithrd
From: smithrd@inteloa.intel.com (Randy D. Smith)
Newsgroups: comp.windows.x,comp.terminals
Subject: Re: Visual 640's and fonts via NFS
Message-ID: <4036@omepd.UUCP>
Date: 9 Jan 89 17:20:48 GMT
References: <807@mentor.cc.purdue.edu>
Sender: news@omepd.UUCP
Reply-To: smithrd@inteloa.UUCP (Randy D. Smith)
Organization: BiiN (tm), Hillsboro, Oregon
Lines: 25

In article <807@mentor.cc.purdue.edu> mjs@mentor.cc.purdue.edu (Mike Spitzer) writes:
>If I try xlsfonts after doing this, I get something like:
>
>NFS error on server mentor.cc.purdue.edu: /usr/local/lib/X11/fonts/: Permission denied
>NFS error on server: /usr/local/lib/X11/fonts/: Not connected

This says to me that you've got the Visual doing all it can do.

>Has anyone gotten this to work?  (My firmware is dated Nov 23 1988, if
>that matters)

It works for me, but I admit that I initially got the same error message
until I was explicit about the precise location of the fonts.  Not knowing
NFS, I had thought that I merely had to export the file system containing
the fonts, but noooo...., in our setup it wanted to know the exact directory
containing the fonts.

Keep trying, but focus on NFS and not the Visual; it works very well indeed.
The reward is worth it, in that xlsfonts will grow positively weary of listing
the enormous number of fonts that will become available to it :-).
--
					Randy D. Smith
			  BiiN (tm)  An Information Systems Company
			     ...uunet!tektronix!inteloa!smithrd
					(503) 696-4660