Xref: utzoo comp.unix.misc:1316 comp.unix.programmer:1605 comp.unix.questions:30512 rec.games.mud:3221 alt.sources:3622
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uwm.edu!bionet!agate!root
From: dburr@.berkeley.edu (Donald Burr)
Newsgroups: comp.unix.misc,comp.unix.programmer,comp.unix.questions,rec.games.mud,alt.sources
Subject: MUD/Robot ports to SysV w/o networking???
Message-ID: <1991Apr18.100948.18632@agate.berkeley.edu>
Date: 18 Apr 91 10:09:48 GMT
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: UC Berkeley Open Computing Facility
Lines: 25

A while back, a guy (john@jwt.uucp, jwt!john@uunet.uu.net) ported TinyMUD
to SysV without networking.  This works great; I'm running it on my old
Callan 300, and it works like a charm.

My question is, has this port been made for any other flavors of MU*?
In the docs for TinyMUSE/MUSH, it says they were working on a SysV with
no networking port of this; is it done yet?  Is a non-networking SysV
port done for TinyMUCK yet?

If not, what type, and how much,  work would it involve to take the
ports made to MUD, and apply them to MUCK/MUSH/MUSE/etc?  Are the
"interface.c" for MUD/MUCK/etc that different, and where are the
differences?

Another question: What would I need to change in Mass-Neotek robots to
get them to "talk" to my MUD?  Where is the "interface" coding for the
robots done?

Please mail replies to dburr@ocf.berkeley.edu.  I'd be happy to respond
with a summary to anyone who wants it, or even post it on the Net if
there's enough demand.
=======================================================================
Donald Burr; Univ of California, Berkeley | America Online: DonaldBurr
INTERNET: dburr@ocf.Berkeley.EDU          |_Compu$erve:_72540,3071____________
      or: 72540.3071@compuserve.COM       |    "Send flames to /dev/null."