Date: Sat, 29 May 93 04:30:07 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 #138
To: tcp-group-digest
TCP-Group Digest Sat, 29 May 93 Volume 93 : Issue 138
Today's Topics:
10Ghz Packet links anyone????
Hints for Getting & Compiling NOS base code (2 msgs)
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, 27 May 93 23:09:49 GMT
From: Mike Dent <g6phf@g6phf.ampr.org>
Subject: 10Ghz Packet links anyone????
To: tcp-group%ucsd.edu%kelvin.usup.uk22.bull.co.uk@switch.UCSD.EDU (Tcp-Group Digest)
Hi, I sent a message to the group a while back asking if there was a better
place to post something like this, but got no reply....so here it is :)
Is anybody out there using 10Ghz microwave radio links for packet??? If so
can you spare any information on your setup. Or at least point me in the
right direction for getting some info please. e.g. what hardware are you
using for the radio side? What gear are you using from the computer to radio.
I'm mainly interested in getting a medium/high speed, point to point link
for tcp/ip useage here in the UK.
Any help/tips would be most welcome! Thanks in advance,
Mike.
--
*******************************************************************************
* Mike Dent * INTERnet---g6phf@kelvin.usup.uk22.bull.co.uk *
* Morecambe * AMPRnet----g6phf@g6phf.ampr.org or g6phf@switch.g6phf.ampr.org *
* Lancs, UK * BBSnet-----G6PHF@GB7ULV.#14.GBR.EU *
*******************************************************************************
------------------------------
Date: Fri, 28 May 1993 09:33:43 -0600 (CST)
From: "Erik Olson" <erik@marge.phys.washington.edu>
Subject: Hints for Getting & Compiling NOS base code
To: tcp-group@ucsd.edu
Okay, a few of you sent me "me too"s regarding my query on retreiving the
new base code. So I figured it out, and here's how:
---
Erik Olson (in lab) erik@marge.phys.washington.edu
University of Washington olson@phys.washington.edu
Cosmic Ray Lab, Phys. 405
HOW TO "QUICKLY" RETREIVE AND COMPILE THE NEW NOS BASE CODE:
1. Ftp the following files from ucsd.edu:/hamradio/packet/tcpip/ka9q
rcs56b.zip
rcsdsrc.zip
unzip.exe (if you need it)
config.h
makefile.
2. Put the executables from rcs56b.zip where you can run them, ie on
the path. (I use c:\bin for this purpose.)
3. Make your working (compilation) directory, ie: c:\nos,
and an RCS subdirectory, ie: c:\nos\rcs.
4. Put the contents of rcsdsrc.zip, the RCS versions of the source code,
into c:\nos\rcs. Put config.h and makefile into c:\nos
5. Now here's where it gets a little hairy. You need to "checkout"
the RCS format files (which themselves are not compilable because
they contain not only the current source but also all the revision
information). To checkout a compilable source file, run the program "co"
FROM THE C:\NOS DIRECTORY. For instance, to get the file popserv.c,
you would type
co popserv.c
You need to do this for EVERY file in the distribution. A couple
ways one can try this:
a. manually check out every file name. Blech.
b. create a .bat file like this:
"dir RCS > getme.bat", then edit getme.bat to trim the excess
junk off the end of each line and add "co " to the beginning.
c. Use some automated tool to create the batch file for you. This is
what I chose to do... I wrote a quick C program to convert the
output of "ls" into a batch file of co's.
6. Hooray! You now have the \NOS directory filled with source code.
Now edit config.h to change options as needed, and Makefile to switch
compilers or compiler switches :) (Makefile is configured for Borland C++ 3.1
on a 386 as default). My personal favorite switch to add is
"-w-par", which surpresses the zillion "Parameter not used" warnings
while compiling.
7. Type "make". Get a cup of coffee. Go out to lunch. If all goes
well, you will have a finished net.exe.
Some Other Things I learned while attempting all this:
* RCS is cool if you know how to use it. If you have access to a
unix system with pic and troff, you can print out the documentation
(it's the file rcs.ms in RCS55a.zip). I have a postscript version of
the manual for those interested.
* Step 5 is not supposed to be as hard as it is. It is that way
because of DOS's filename size limitations and the new RCS's decision
not to add a "%v" at the end of the RCS format files. [This
information from Phil Karn.] Hopefully this will improve in the future?
Anyway, hope that clears up some problems for some of us. Happy Compiling!
- Erik
------------------------------
Date: Fri, 28 May 1993 18:59:20 -0400 (EDT)
From: MIKEBW@ids.net (Mike Bilow, <MIKEBW@ids.net>)
Subject: Hints for Getting & Compiling NOS base code
To: erik@marge.phys.washington.edu, tcp-group@ucsd.edu
To make a raw list of filenames from a directory under MS-DOS 5.0 or
later, issue the DIR command with the "/b" switch. This produces a
"bare" listing. For example, "DIR *.c /b > all_c.lst" will find all
of the *.c files in the current directory and put their names into
file all_c.lst, one filename per line. This can significantly speed
up the "co" processing discussed.
-- Mike Bilow, <mikebw@ids.net> (Internet)
N1BEE @ WA1PHY.#EMA.MA.USA.NA (AX.25)
------------------------------
End of TCP-Group Digest V93 #138
******************************
******************************