<HEAD><TITLE>discuss@charon: [279] in "Coldmud discussion meeting"</TITLE>
<H1>[279] in Coldmud discussion meeting</H1></HEAD>
<A HREF="/"><IMG SRC="/i-d.gif" ALT="root"></A>
<A HREF="?279"><IMG SRC="/i-back.gif" ALT="meeting"></A>
<A HREF="/help.html"><IMG SRC="/i-help.gif" ALT="help"></A>
<A HREF="1"><IMG SRC="/i-first.gif" ALT="first"></A>
<A HREF="258"><IMG SRC="/i-fref.gif" ALT="first in chain"></A>
<A HREF="278"><IMG SRC="/i-pref.gif" ALT="previous in chain"></A>
<A HREF="278"><IMG SRC="/i-prev.gif" ALT="previous"></A>
<A HREF="280"><IMG SRC="/i-next.gif" ALT="next"></A>
<A HREF="280"><IMG SRC="/i-nref.gif" ALT="next in chain"></A>
<A HREF="302"><IMG SRC="/i-lref.gif" ALT="last in chain"></A>
<A HREF="1641"><IMG SRC="/i-last.gif" ALT="last"></A>
<HR><H2>Re: ports</H2>
<H3>daemon@ATHENA.MIT.EDU (Fri May 20 03:52:30 1994
)</H3>
<PRE>
Date: Fri, 20 May 1994 01:49:29 -0600 (MDT)
From: the Lyncx &lt;BRANDON@cc.usu.edu&gt;
To: coldstuff@MIT.EDU
X-Vms-To: COLDSTUFF

&lt; I would really like to see the services implemented as one port as this would
&lt; actually simplify access. A 'services' server would run, allowing services
&lt; to 'register' themselves as available in the db.
[snip]

Ok, once again.  In the above listing that service _is_ there.  It is the
portmapper port.  However, I think that we should not do just one or the other,
but rather both.  Have a few basic "known" ports (such as login and fingerd),
and if the server wants to it can expand beyond these known ones, through the
user of portmapper.

-Brandon-
</PRE>
