Date: Sun, 2 Jan 94 04:30:02 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 #341
To: tcp-group-digest
TCP-Group Digest Sun, 2 Jan 94 Volume 93 : Issue 341
Today's Topics:
Change those address books...
idea
JNOS Documentation (2 msgs)
Suitable C compiler for NOS?
tnos-topics group
TNOS Availabilty & Mailing List
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, 01 Jan 94 12:50:10 EST
From: brian@lantz.cftnet.com (Brian A. Lantz)
Subject: Change those address books...
To: tcp-group@ucsd.edu
Well, it's a new year, and new work and Internet data for me. IF you knew
the old IP address, change it to brian@lantz.cftnet.com. This is my home
PPP IP system, and will serve as TNOS CENTRAL.
Also, I am no longer Manager of Software Development at PacComm. I am now
employed as a Communications Specialist with Technology Management
Associates. I will still be pitching in around PacComm as a consultant.
And in regards to TNOS, there will be a mailing list for TNOS specific
Q & A starting up (probably by the first of the week). I'll post another
message with the details.
TNOS distribution will be PRIMARILY based of of lantz.cftnet.com and
the PacComm landline BBS. I will encourage any and all comers to place
it ANYWHERE they wish, but I will only be maintaining limited sites. I
would not be against mirroring my site with a directory at ucsd.edu,
if it is possible (Brian will need to decide this).
Hope everyone has all of the finest in 1994!
/----------------------------------------------/
/ Brian A. Lantz/KO4KS /
/ /
/ Packet: KO4KS@KO4KS.#TPAFL.FL.USA.NA /
/ Internet: brian@lantz.cftnet.com /
/ Live long, and prosper! /
/----------------------------------------------/
------------------------------
Date: Sat, 1 Jan 1994 09:28:20 -0600 (CST)
From: root@raider.raider.net (Mark J. Bailey [HOME])
Subject: idea
To: tcpgroup@ucsd.edu
Hi,
I have a question/suggestion.
I have worked with a few packages (network packages that is) that run under
unix and you have the option to send "trace" output to the syslog(3) facility
under unix. For those of you that don't know of unix and/or syslog(3), syslog
is a progam/daemon that allows one to use a unix library call syslog(3) to
have a systematic way for an application to "report" various things to the
system logging facility (such as "bill logged in" or "disk space low" or
"illegal user access attempted" etc etc) by this one library call. All
syslog(3) logged items from various applications on a system using that API
usually go to /usr/spool/mqueue/syslog (or whatever).
While I am not trying to advocate that NOS be able to report to syslog(3) in
particular, something of some nature would be nice that would allow the
remote operator to ping, turn on and watch tracing, do trace routes, etc.,
while not having to be at the console. Now, this may already be possible,
but if so, I am unaware of it and have been running a NOS wormhole for a
couple of years now. It would be nice if NOS could report to syslog(3)
for things like usage statistics, user logins, mail arrival, etc. Also
to report things like file transfers, disk space conditions, nodes that
seem to have "died". I am just throwing these out off the top of my head.
PC Route does this by having the user give the IP number of the unix system
that it will log to using the destination system's syslog(3) facility.
Of course, this would not be much use to DOS only users (I don't think).
Something else that I thought would be an interesting twist to this would be to
configure a special socket/port to also have NOS send trace output, etc.,
to. Ie, lets say that we choose port 2500. Me as a remote "sysop" could
telnet the NOS node as follows:
telnet 44.34.51.29 2500
and the I could see all the same output that trace sends to the "screen" on
the F9 key (I am running WG7J 1.10x9).
Is this far out or feasible? Many times we have needed to see what was
happening on the ethernet port but were remote and did not have that vantage.
Just general ramblings....
Mark
------------------------------
Date: Sat, 1 Jan 1994 18:00:08 -0700 (MST)
From: Klarsen <klarsen@acca.nmsu.edu>
Subject: JNOS Documentation
To: tcp-group@ucsd.edu
The hams looking for documentation on jnos should look into the
/hamradio/packet/tcpip/wg7j directory on ucsd.edu and d/l the latest
version of jnos there. It includes a "readme" file of about 25 pages that
tells you much on how it works.
Johan suggests that you find the documentation for the PA0GRI v
2.0 docs called "nos_1229.man". I have it but forget where I got it. These
2 sources have been combined by me into a jnos manual. If my wife will let
me retire I plan to finish that work first thing. But it doesn't look
good... she just bought a new Toyota Camray with all the trimmings after I
just bought a new Jeep! I fear work I must for another year to pay of this
stuff....
73 de karl sk
------------------------------
Date: Sat, 1 Jan 1994 22:07:21 -0600 (CST)
From: ssampson@sabea-oc.af.mil (Steve Sampson)
Subject: JNOS Documentation
To: TCP-Group@ucsd.edu
The jnos-doc.msword file I uploaded is basically a first pass.
What I did was take several files from ucsd.edu and format them
to remove all the spaces and such, down to a raw wordprocessor
format. I use Wordperfect but the interest was from an MS Word
user so I translated it to that before upload. The only other
thing I did was renumber the chapters and translate the document
to English, and spell-check it. It had some Scandinavian English
in there :-)
It will probably save someone a bunch of time to start with this
file. It's been sitting on my computer since August without any
progress so I offer it as a helpful start. Down about 3/4 of the
way is the parts that need to be moved up to the proper sections.
It's just tedious, not hard.
I believe I was using JNOS from about 2 versions ago, so it's
probably out of date, and needs fine tuning after all the moving.
--
Steve
------------------------------
Date: Sun, 2 Jan 1994 22:25:10 +1030 (CST)
From: gwillis@eleceng.adelaide.edu.au
Subject: Suitable C compiler for NOS?
To: tcp-group@ucsd.edu
Hello!
I am currently looking to purchase a C compiler and eventually have
intentions of dabbling with the Nos sources to generate my own versions
and compile others work into executables etc.
What is the current prefered C compiler among the Nos authors? I must
admit I currently have only a very limited knowledge of C, the compiler
I get would initially be used to help be become more proficient before I
start attacking any of the projects I have in mind. Still, I might as well
get a compiler that will happily work with the code that I eventually
wish to play with.
Cheers de Grant VK5ZWI
--
Grant Willis - VK5 WIA, SCARC, SAPUG | Vacant Space.....
Internet: gwillis@eleceng.adelaide.edu.au | Cheap Rates - Apply within!
Packet Radio: VK5ZWI@VK5TTY.#ADL.#SA.AUS.OC +-----------------------------
Disclaimer: Thoughts expressed here are not those of any organisation.
------------------------------
Date: Sat, 01 Jan 94 22:43:58 EST
From: brian@lantz.cftnet.com (Brian A. Lantz)
Subject: tnos-topics group
To: tcp-group@ucsd.edu
A reminder, as with all groups, if any special SMTP servers or MX
records are needed to get mail to you, please supply these in a personal
message to me so I can get your mail to you.
I need this info for:
segrest@bobseg.enet.dec.com
samalott@sampc.cmhnet.org
Thanks
/----------------------------------------------/
/ Brian A. Lantz/KO4KS /
/ /
/ Packet: KO4KS@KO4KS.#TPAFL.FL.USA.NA /
/ Internet: brian@lantz.cftnet.com /
/ Live long, and prosper! /
/----------------------------------------------/
------------------------------
Date: Sat, 01 Jan 94 20:12:44 EST
From: brian@lantz.cftnet.com (Brian A. Lantz)
Subject: TNOS Availabilty & Mailing List
To: tcp-group@ucsd.edu
TNOS - The Undiscovered Country
I expect to have release 1.00 of TNOS available by anonymous FTP by the
first part of the week from lantz.cftnet.com. Sometime around Tuesday
or Wednesday I hope to have it all ready to grab.
I am also starting up a TNOS tips/Q&A/support mailing list, running off
my TNOS system. If you wish to join:
Send subscription additions and deletions to:
reqsvr@lantz.cftnet.com
To subscribe:
send Subject "group subscribe tnos-topics"
To Unsubscribe:
send Subject "group unsubscribe tnos-topics"
Send all submissions to "tnos-topics@lantz.cftnet.com"
The Request Server will send you back a VERY short reply, to confirm
it's success. There will be times when the system will be down, but the
SMTP mail is queued. If it is up, the reply will be very quick.
If you are curious as to what all the server will handle,
you can send the Subject "help" and it will send you back its docs.
I will put together a charter for this group in the next few weeks.
This will be the first REALLY heavy beating on the Request Server, so be
patient if problems arise (it has been put through the paces, though).
/----------------------------------------------/
/ Brian A. Lantz/KO4KS /
/ /
/ Packet: KO4KS@KO4KS.#TPAFL.FL.USA.NA /
/ Internet: brian@lantz.cftnet.com /
/ Live long, and prosper! /
/----------------------------------------------/
------------------------------
End of TCP-Group Digest V93 #341
******************************
******************************