Date: Fri, 18 Jun 93 04:30:11 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 #157
To: tcp-group-digest
TCP-Group Digest Fri, 18 Jun 93 Volume 93 : Issue 157
Today's Topics:
Amateur Radio
ampr.org robot
Looking for *nix suggestions...
NOS SMTP Server Patch/bugfix for control-Z's
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: Fri Jun 18 14:09:32 1993
From: iiitac@pyr.swan.ac.uk
Subject: Amateur Radio
To: tcp-group@ucsd.edu
Most of the Unixes will do what you want. Normally people run WAMPES or
KA9Q in some form and run a slip link from the KA9Q software to the kernel
TCP/IP over a pty. On some poorer unixen you'll need to use a pair of
looped back serial ports, which is a pain.
I run Linux and WAMPES and I'm very happy with it.
Alan
------------------------------
Date: Thu, 17 Jun 93 22:39:51 PDT
From: brian@nothing.ucsd.edu (Brian Kantor)
Subject: ampr.org robot
To: tcp-group@ucsd.edu
Looks like the ampr.org robot (ampraddr@ucsd.edu) has suffered from
database damage. I'll see if I can get it fixed somehow but don't hold
your breath - in less than 24 hours I leave town for a week and I just
don't know if I'll be able to get it working that fast. Arrrgh!
- Brian
------------------------------
Date: Wed, 16 Jun 93 8:36:00 EDT
From: "John R. Ackermann" <jra@law7.daytonoh.ncr.com>
Subject: Looking for *nix suggestions...
To: tcp mailing list <tcp-group@ucsd.edu>
I've been running an NCR Tower Unix system (68020 based) at home for a
couple of years, hooked by ethernet to a PC running JNOS which serves as
a router to the radio world. My goal is to offer mail, news, and
database services to the ham community via tcp/ip.
Last week I took a lightning hit that wiped out two of my PCs, and a
couple of pieces of the Tower.
It looks as though the insurance proceeds <might> let me do some
upgrading, and I'm considering retiring the Tower and replacing it with
an Intel-based box running Unix.
One of my goals would be to eliminate the need for another PC to serve
as a router to the radios.
I'm considering 386BSD, the BSDI version, Linux, Destiny (SVR4.2.2?), and
I may be able to get my hands on a slightly old copy of SCO unix as a
freebie. I'm not a Unix guru, so I'm looking for something that'll be
reasonably stable running TCP/IP and UUCP. I also need something that I
can get a simple indexed DBMS system for -- I run a callbook and
frequency database server.
I'm particularly interested in an OS that's either a) likely to have
AX.25 hacked into the kernel soon, or b) has a decent DOS emulator that
might let me run JNOS in a DOS session to serve as the router -- is this
practical, or am I in fantasy land?
If the insurance company is nice, I'll be able to pay some money for the
OS instead of sticking with 386BSD or Linux, if doing that will buy what
I need.
Thanks for any suggestions...
73,
John AG9V
------------------------------
Date: Thu, 17 Jun 1993 17:19:28 -0600 (CST)
From: "Erik Olson" <erik@marge.phys.washington.edu>
Subject: NOS SMTP Server Patch/bugfix for control-Z's
To: tcp-group@ucsd.edu, karn@qualcomm.com
Askhok Aiyar (ashok@biochemistry.cwru.edu) had a problem wherein certain
PC mailers were passing control-Z's (created in some signature files by
older editors). The problem is that the control-Z passes through the TCP
connection and eventually gets written to the eventual recipient's mail file
on the NOS machine. Next time one (POP,MAILBOX, et. al.) tries to read from
the file, the control-Z is interpreted as end of file and everything after
it (including the subsequent messages!) are discarded.
I have written a quick 2-liner fix for this. For the current base code
(smtpserv.c, rev 1.18), here are the diffs:
354a355,356
> while (strchr(p,CTLZ)!=NULL) /* Change control-Z's to \n */
> *strchr(p,CTLZ)='\n';
and for those who need a context of where to put those two lines, they come
right in this section (code may differ slightly based on nos version):
/* Append to data file */
/* CHANGE GOES IN HERE */
if(fprintf(mp->data,"%s\n",p) < 0){
(void) usprintf(mp->s,Ioerr);
return 1;
}
- Erik
---
Erik Olson (in lab) erik@marge.phys.washington.edu
University of Washington olson@phys.washington.edu
Cosmic Ray Lab, Phys. 405
------------------------------
End of TCP-Group Digest V93 #157
******************************
******************************