Date: Thu, 4 Nov 93 04:30:06 PST
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 #286
To: tcp-group-digest
TCP-Group Digest Thu, 4 Nov 93 Volume 93 : Issue 286
Today's Topics:
AMPR gateways on Internet
AX.25 code for SunOS....
Desperate cry for help!
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: Wed, 3 Nov 93 08:03:00 -0600
From: sbrown@charon.dseg.ti.com (Steve Brown)
Subject: AMPR gateways on Internet
To: karn@qualcomm.com
Phil writes:
> In as much as I was the one who originally created the facilities that
> made it so easy to use the Internet in the construction of an amateur
> network, it should be no suprise that I have no problem with doing so.
>
> I consider myself a computer communications person first, and a radio
> amateur second.
I believe this sentence defines the whole discussion. Those of us who
consider themselves radio amateurs first and computer communications
persons second would prefer that the radio aspects of the situation
receive more attention than the computer aspects.
> Particularly in emergency communications, you *really*
> want to be able to use whatever you have on hand; I don't think the
> people we'd serve in such a situation could give a damn whether you give
> them a radio link, a wire link or a waxed string, as long as it works.
Couldn't agree more.
> And as hobbyist experimenters, we hams also have a long tradition of
> scrounging up whatever is available (particularly surplus items) and
> doing clever things with it. Building radio/Internet/whatever hybrids
> just continues this tradition. What's wrong with that?
Nothing is wrong with that. IMHO, it is just a question of priorities.
Also IMHO, the radio side of the discussion ought to receive a higher
priority than the computer side.
*********************************************
| Steve Brown, WD5HCY | |
| sbrown@charon.dseg.ti.com | Simplicate |
| wd5hcy@wd5hcy.ampr.org | and add |
| [44.28.0.61] | lightness. |
*********************************************
------------------------------
Date: Thu, 4 Nov 93 01:16:36 -0500
From: mo@uunet.uu.net (Mike O'Dell)
Subject: AX.25 code for SunOS....
To: tcp-group@ucsd.edu
i seem to remember that backin the dim past (circa the colo spgs
packet meeting) that someone did AX.25 code for SunOS that ran
through the zs driver and hence could share the serial port
with other stuff. am I misremembering this???
-mo
------------------------------
Date: Wed, 3 Nov 1993 15:51:11 -0100 (GMT-1:00)
From: andy@mimuw.edu.pl (Andrzej K. Brandt)
Subject: Desperate cry for help!
To: tcp-group@ucsd.edu
Hello everyone,
I'm once more asking you to help me. I can't get working sources of original
KA9Q's NOS. I downloaded RCSDSRC.ZIP from UCSD.EDU. Then, after some battle
with RCS (some clever fellow decided that it would be a nice idea to supply
manuals for DOS version in UNIX man format) I did co on every file from that
archive and got something, that shoudl be working sources of NOS. However it
won't compile - there are no some files for fax, namely qfax2.c. I commented
whole CDMA library but that just gave me next errors - for example something
called Kdebug in main.c seems to be not defined anywhere.
I want to make some experiments with NOS and to look how it works inside,
but to start I need a good source that will compile without problems. Please
help me! I don't know where I can get it! Maybe I did something wrong with
RCS. I use BC++ 3.1 BTW, so the problem is not here.
The second problem is screen management in latest NET.EXE that I downloaded
from ucsd.edu after realising that I won't be able to compile it from the
sources. That problem is that when something is attached on asy with 9600
bauds, things writen to NET and by NET don't appear on the screen until next
screen swap (for example entering and leaving a session). As far as I
remember that problem was present in previous relases too, but then I was
using various packet drivers and I didn't care about it.
I know that such a questions are lame and make you all laugh, I know that
I'm not from US and my english is not so good, I know that I'm not one of
the gurus worth speaking with, but maybe someone will remember that he
wasn't born with all his clevernes and had to learn. That's what I want to
do. And I don't any better place to turn with these questions than this
list. So - if you know the answers and have a second to spare, please e-mail
me.
--
73 de Andy SP5WCA
/-------------------+--------+-------------------+-------------------------\
I Andrzej K. Brandt I SP5WCA I andy@mimuw.edu.pl I sp5wca@sp5pbe.wa.pol.eu I
\-------------------+--------+-------------------+-------------------------/
------------------------------
End of TCP-Group Digest V93 #286
******************************
******************************