Date: Fri, 16 Apr 93 04:30:08 PDT
From: Advanced Amateur Radio Networking Group <tcp-group@ucsd.edu>
Errors-To: TCP-Group-Errors@UCSD.Edu
Reply-To: TCP-Group@UCSD.Edu
Precedence: Bulk
Subject: TCP-Group Digest V93 #100
To: tcp-group-digest


TCP-Group Digest            Fri, 16 Apr 93       Volume 93 : Issue  100

Today's Topics:
                          It works?? but....
                 x.500 service for Internet amateurs?

Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.

Archives of past issues of the TCP-Group Digest are available
(by FTP only) from UCSD.Edu in directory "mailarchives".

We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party.  Your mileage may vary.  So there.
----------------------------------------------------------------------

Date: Thu, 15 Apr 93 15:56:52 EDT
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: It works?? but....
To: nos-bbs@hydra.carleton.CA

When I went thru and cleaned up the 108 code (result 108df) I basically
ignored the twin/gracilis driver code. In fact I put an ifdef around
it so I would not see the errors. I do not use nor need the code here.

A local user asked me to compile a version with that module in and since
I no longer compile with prototype errors turned off I saw the errors
again. I thought I would give a stab at cleaning it up but I gave up
when I realized that it would take a good deal of work.

Would whoever is responsible for writing 'twin_dr.c', 'twin_at.c' and
'gracilis.c' PLEASE go thru the code and add prototypes. Prototypes for
all functions in twinxxx.c should go in twin.h and in gracilis.h for
gracilis.c. In addition you will have to fix some of the function calls
so that the prototype matches the calls.

I got as far as adding most of the prototypes and had all kinds of wrong
types in calls, two many or two few parameters etc. The code definitely
needs some cleaning up. This is a prime example of why we SHOULD be using
prototyping!!

It is hard to say if this is causing any severe problems but it sure is not
helping.

By the way users of the 108df code have reported less problems. This is
at the moment very unscientific but encouraging.

I call upon anyone who wrote code in the past for NOS to go back and
look it over (based on 108df or Johan's next release). No errors should
be reported with prototype warnings turned ON - the default - -w-pro REMOVED
from the makefile compiler options.

Doug

------------------------------

Date: Thu, 15 Apr 1993 18:05:32 -0600
From: ke9yq@ke9yq.ampr.org (Bob Van Valzah, ke9yq)
Subject: x.500 service for Internet amateurs?
To: tcp-group@ucsd.edu

I just played around with the x.500 server on ds.internic.net and was
favorably impressed.  (Login as x500 with no password to try it out
yourself.)  Considering the number of amateurs reachable via Internet mail,
I think it'd be nice to have an x.500 server to keep track of their names
and addresses.  (I can't tell you how many times I've know Joe Schmo's name
or call, but didn't know or had lost his E-Mail address.)  The database
could be maintained with a "robot" mailer much like is used to maintain the
.ampr.org DNS.  Has anybody else given this any thought?  I understand that
such a server requires the ISODE which is no small piece of code, but it
should fit a suitably equipped 486, shouldn't it?

73, Bob, ke9yq

------------------------------

End of TCP-Group Digest V93 #100
******************************
******************************