[198] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next last

Re: /etc/services

daemon@ATHENA.MIT.EDU (Fri Apr 1 12:06:11 1994 )

Date: Fri, 1 Apr 94 18:01:09 BST
From: Andrew Wilson <Andrew.Wilson@cm.cf.ac.uk>
To: coldstuff@MIT.EDU

----- Begin Included Message -----

From BRANDON@cc.usu.edu Fri Apr  1 17:49:34 1994
Date: Fri, 01 Apr 1994 09:45:42 -0600 (MDT)
From: the Lynx <BRANDON@cc.usu.edu>
Subject: /etc/services
To: coldstuff@MIT.EDU
Mime-Version: 1.0
Content-Transfer-Encoding: 7BIT
Content-Length: 945

I've been thinking lately (ouch).

why don't we define up a bunch of "services" or ports that all coldmuds should
listen to, just as a standard, for various different things, such as

smtpd (same as SMTP, protocol and all)             6625
nntpd (hsm, brainstorm)                            66119
httpd                                             <ack, dont know the usual
                                                   httpd port, 66 + whatever>
faucet (it just spams something, like inet faucet) 6663
rcommands                                          6664
coldlink (funky idea with ...stuff :)              6665
connection                                         6666

Anyhow, comments?  the coldlink port is an idea I have for doing expanded
server->server linking, which would include passing minor attributes of a user.

We could also figure up some other link aspects (distributed stuff?)


----- End Included Message -----

Aigh, Caramba!  Remember that  MOO is gearing up for multiple ports soon, now
would be a good time to share your thoughts with the likes of Pavel C.  It'd
be a shame if every M** server on the inet had a different standard set of


Andrew Wilson
<a href = http://www.cm.cf.ac.uk/People/Andrew.Wilson.html>Ay</a>