Date: Mon, 18 Jan 93 04:30:13 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 #18
To: tcp-group-digest
TCP-Group Digest Mon, 18 Jan 93 Volume 93 : Issue 18
Today's Topics:
Calling Alan Cox
Ckarkson driver v 10
Ethernet on the air
Future of NOS
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: Sat, 16 Jan 93 02:21:14 MET
From: G4KLX%PI8VNW@pa2aga.ampr.org
Subject: Calling Alan Cox
To: TCPAGA@pa2aga.ampr.org
into contact with Alan Cox (iiitac@pyr.swan.ac.uk) to talk to him about Linux
and NOS. Since I don't have two way access to the Internet could he (you)
contact me on normal packet so that we can have a meaningful exchange of views.
Please mail me G4KLX @ GB7HMZ it should get here in less than a day I reckon.
Jonathan Naylor
For the Jihad:
I like: OS/2 RISC-OS UNIX MVS
I don't like: Windows DOS OS/400
PLEASE reply to the list, NOT to the From: address
because this mail is sent through a one-way gateway!
------------------------------
Date: Sun, 17 Jan 93 18:27:02 CET
From: BARRY TITMARSH <BTITMARS%ESOC.BITNET@vm.gmd.de>
Subject: Ckarkson driver v 10
To: TCP-GROUP <TCP-GROUP@ucsd.edu>
Can some one point me to the ftp location of the latest version 10
drivers pack from Russ Nelson
FTP via mail is a bit slow just now and it saves me a big search.
thanks barry.
------------------------------
Date: Sun, 17 Jan 93 16:57:30 CST
From: jrc@brainiac.mn.org (Jeffrey Comstock)
Subject: Ethernet on the air
To: tcp-group@ucsd.edu
If anyone has 10mb/s running on the air (CQ Glenn Elmore/Bdale Garbee), please
send email to jrc@brainiac.mn.org about it. I mainly want to know if
it works, and how you are doing it....
------------------------------
Date: Sun, 17 Jan 1993 23:37:52 -0600 (CST)
From: MSgt S. Sampson <ssampson@sabea-oc.af.mil>
Subject: Future of NOS
To: TCP-Group@UCSD.Edu
Brian Kantor writes:
> I run this mailing list in the increasing-forlorn hope that it
> will be used to advance the state of the art of ham radio
> networking, specifically by the use of the internet protocols
> and other sophisticated techniques.
Actually whenever someone discusses advanced networking or
concepts it is met with silence (probably alot of private mail
ensues, but nothing gets into the group output), while the
conversion of NOS to a BBS has been the primary thrust of this
group in the last year. Actually NOS is a pretty good BBS now,
so maybe we can disable all that IP and TCP stuff :-) Actually
the whole BBS exercise is a total waste of time because nobody
actually reads all that crap. We have a guy locally that
dutifully has been uploading ARRL bulletins from RTTY to Packet
for years. He hasn't noticed that no one has been downloading
them...
After playing with IP on 1200 and 9600 Ham Radio for the past
year, I've come to the conclusion that it is way too manual.
Too much operator activity to get where you're going (sort of
like the manual Air Defense systems of the sixties that had
operators slewing the height antenna). The user level Telnet
and FTP are probably fine for historical traditions, but are
really obsolete for the 90's. If the object is to connect the
Internet to a radio, then I can say it has been accomplished,
and the FTP and Telnet schemes work over radio just like wire
(only painfully at 1200). But Telnet and FTP at the Ham radio
level, don't do anything better than what the built-in features
of the TNC do, and then requires an IBM Clone computer on top of
that. The protocols seem only beautiful to geeks and nerds
(like me)...
I'd like to think there are much better ways to automate what it
is we really want from our clones and Ham radio. It can use IP
and TCP or whatever, but it shouldn't include a Unix login
prompt that is so popular with the current Ham IP
implementations. A program thats been around for awhile is a
simple DOS program that creates a network using the serial port
(cheaplink). (A person could probably insert a TNC at this
point). Taking this a step further would create remote disk
addresses using a persons callsign. Or, I assign IP addresses to
drive symbols and then when I switch to the G: drive and do a
DIR it gives me what I want. Sort of like a slow speed NOVELL.
I can then just use my DOS copy command, etc. The object being
to put NOS below DOS (on a card preferably) and produce DOS
applications to do CHAT and FILE operations other than
pretending we're a Unix machine with login administration and
all that garbage. You could leave that module in for people who
use NOS on the Internet, but for Ham Radio it's a waste of time.
It seems the last month had alot of the trade magazines talking
about the ATM protocol (Asyncronous Transport Method - I think
that's what the acronym was). None of them showed technically
what was going on, other than to say that it was a fixed length
53 byte frame which includes a 5 byte address. Seems this
protocol is geared toward voice and video, and other burst type
data. Since the end game of all this is to produce a box that
does data and voice equally well, maybe someone can introduce us
to that protocol or direct us to online materials that explain
it.
---------
Steve Sampson/N5OWK Oklahoma City
------------------------------
End of TCP-Group Digest V93 #18
******************************
******************************