Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Webster via remote logins. Is it possible?
Summary: Available by anonymous FTP from sutro.sfsu.edu
Message-ID: <184@toaster.SFSU.EDU>
Date: 11 Dec 89 13:33:04 GMT
References: <1989Dec10.195312.18995@zaphod.mps.ohio-state.edu>
Reply-To: eps@cs.sfsu.edu
Organization: San Francisco State University
Lines: 36

In article <1989Dec10.195312.18995@zaphod.mps.ohio-state.edu>,
	nevai@function.mps.ohio-state.edu (Paul Nevai) writes:
> Is it possible to use Wbster via remote logins?

Sure.  There are two pieces: websterd, a TCP server that will run
on any NeXT, and webster, a client that will run on any UNIX
system that talks TCP (including the NeXT).

In ~ftp/pub on sutro.sfsu.edu:

The file NeXT-websterd.shar is Steve Hayman's server program.
Read the enclosed instructions about setting the oknets[]
array--and remember to list net 127 so you can access it
from your own machine!  You will have to add a line to services
in netinfo:

x400	103/tcp	dictionary	webster

That's right, it "traditionally" co-opts the x.400 port.
(Except at Stanford, where they advocate 2627)

webster.tar.Z also has a table that needs to be modified, in this
case the hosts that you want to try (in order) for webster servers.
If you're compiling this on a NeXT, the first one should be
localhost.  It works without modification on SunOS and HP/UX, and
shouldn't have any problems on your favorite networked UNIX.
We've even set it up as a login shell for a non-passworded
"webster" username on non-NeXT machines.

There's a webster.el for GNU emacs in this package as well.  I've
found its performance to be somewhat erratic.

As is, as always.  I worked on part of the webster client, but
the rest is strictly not-invented-here.

					-=EPS=-