Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bryan
From: bryan@cs.utexas.edu (Bryan Bayerdorffer @ Wit's End)
Newsgroups: comp.sys.amiga
Subject: Re: Dnet:  Accessing your Amiga from a Unix host;  Mailchk
Message-ID: <457@mohawk.cs.utexas.edu>
Date: 15 Mar 90 04:58:31 GMT
References: <2472@quiche.cs.mcgill.ca> <9010010@hpfcso.HP.COM>
Reply-To: bryan@cs.utexas.edu
Organization: Spam Detection & Removal Squad, Austin, TX
Lines: 18
Spam-Content: Negligible

In article <9010010@hpfcso.HP.COM> stroyan@hpfcso.HP.COM (Mike Stroyan) writes:
=-> 	I stared at dnet.c for an hour today, and cannot see any reason why the
=-> socket that gets created is named 'DNET. ' instead of DNET.3 .  Can anyone
=-> enlighten me?
=-
=-The "DNET. " is coming from the amiga side.  In control.c, do_cmd is sending
=-a PKCMD_ACKRSTART packet with a space character.  That is processed on the
=-unix side by do_cmd in the unix control.c.  It calls setlistenport with the
=-data character sent by the amiga.  The bind in setlistenport then appends
=-the space to "DNET.".
=-

	Aha.  I see it now.  I guess I was misled by the fact that
setlistenport is not declared as external anywhere.  Tsk tsk.  That still
leaves an inconsistency, though.  Presumably the hardcoded '3' should be
changed to a ' ' everywhere.  Geez, Matt, at least use #defined constants in
situations like this!  Better yet, I suppose the -n option for dnet is supposed
to supply this, whenever it finally starts being used.