Date: Fri, 22 Jan 93 04:30:10 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 #22
To: tcp-group-digest
TCP-Group Digest Fri, 22 Jan 93 Volume 93 : Issue 22
Today's Topics:
AmigaNOS help command
if netmask (2 msgs)
nos futures (2 msgs)
RCS (5 msgs)
TIP BBS
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, 21 Jan 93 08:52:25 -0600
From: sbrown@charon.dseg.ti.com (Steve Brown)
Subject: AmigaNOS help command
To: tcp-group@ucsd.edu
Hello Folks,
Apologies if this shouldn't be posted here.
I'm running/trying to run AmigaNOS 2.9g. Everything comes up and seems
to run OK, however, when I try to use the "help" command, there is
a lot of disk activity and the command line prompt returns. The other
window, don't know the official name yet, shows something like
"Arun failed returncode 20 insufficient memory"
Just at this point, the "mem" command yields >600K. I am also able
to get to an AmigaShell at this point and run "less" on the appropriate
file in TCPIP:spool/help (which is, I think, what "help" does) and
have everything work correctly.
Any ideas?
*********************************************
| Steve Brown, WD5HCY | Simplicate |
| sbrown@charon.dseg.ti.com | and add |
| wd5hcy@kf5mg.#dfw.tx.usa.na | lightness. |
| (214) 575-3597 | |
| MSG:SBRN | - Bill |
| MS 8496, PSK0 | Stout |
*********************************************
------------------------------
Date: Thu, 21 Jan 93 13:16:15 GMT
From: A.D.S.Benham@bnr.co.uk
Subject: if netmask
To: TCP-Group@UCSD.Edu
I'm puzzled by the "if netmask ..." command in, well, every NOS I've looked at.
^^
(that's as in interface)
The AUTOEXEC.NOS file I have been using for several years has in it
if netmask tnc0 0x44ffffff
which can't possibly be right (?) as the ampr.org domain is decimal 44
(hexadecimal 2C).
I've tried "if netmask tnc0 0x2cffffff" and also "if netmask tnc0 0x2c000000"
which I found in someone else's AUTOEXEC.NOS file. I've not seen anything
different happening.
The only reference I can find in the documentation for various flavours of
NOS is that the command is related to the default route.
Can anyone shed any light on the use and purpose of the command please? Even
looking through the source code hasn't helped my understanding.
Andrew Benham
--------------------------------------------------------------------
adsb@bnr.co.uk BNR Europe Ltd, London Road, Harlow, Essex CM17 9NA
+44 279 402372 Fax: +44 279 402100
Home: g8fsl@g8fsl.ampr.org [44.131.19.195] G8FSL@GB3XP
--------------------------------------------------------------------
------------------------------
Date: Thu, 21 Jan 1993 21:01:02 -0600
From: miltonm@inetnode.austin.ibm.com (Milton Miller)
Subject: if netmask
To: A.D.S.Benham@bnr.co.uk, TCP-Group@UCSD.Edu
The netmask is the compare-under mask to say a given address is on
a given network. In NOS, it adds an implicit routing table entry
based on the number of ones in the mask. If you want all of net
44 to be routed to a given interface, and that interface has a net
44 address, then you can say if .. netmask 0x00ffffff to set
a route for 44.0.0.0/8 ... (replace ... with interface name both
places).
milton
<I don't speak for IBM>
------------------------------
Date: Thu, 21 Jan 93 13:25:52 EST
From: kz1f@RELAY.WESTBORO.LEGENT.COM
Subject: nos futures
To: tcp-group@ucsd.edu
Jack writes
> "engine" is the same (tcp/ip) He plans to write to the SOM in OS/2. He thinks
> that (for example) treating the SMTP server as an object (rural route
> mailbox) on the desktop metaphors used in OS/2, Next, Sys7, Xwin... etc is
> more intuitive to the non-UNIX j.a.luser.
No.. It is more intuitive PERIOD, even for the unix luser. If people didnt
discover/exploit new and better technology we'd still be counting grains of
sand on the beach. The abacus would be too high tech.
> In the SMTP example, you create a message in "your favorite editor". The
> message become an "object" which is dropped in the mailbox. The mailbox
Not really, the mail envelope would be dropped on the host it was destined to.
The object, envelope, would know how to get there, ie smtp.
I clarify this only because I am underwhelmed with the discussion my remarks
have generated to date and perhaps this my spur more (some) discussion. Perhaps
you all are too enamered(sic) with the latest goodies Johan has cooked up. A
pretty heady responsibility Jo, after all, they "love" you on Long Island.
Walt Corey - kz1f@kz1f.legent.com
----------------------------------
| |
| Space for Rent apply within |
| |
----------------------------------
------------------------------
Date: Thu, 21 Jan 93 13:25:52 EST
From: kz1f@RELAY.WESTBORO.LEGENT.COM
Subject: nos futures
To: tcp-group@ucsd.edu
Jack writes
> "engine" is the same (tcp/ip) He plans to write to the SOM in OS/2. He thinks
> that (for example) treating the SMTP server as an object (rural route
> mailbox) on the desktop metaphors used in OS/2, Next, Sys7, Xwin... etc is
> more intuitive to the non-UNIX j.a.luser.
No.. It is more intuitive PERIOD, even for the unix luser. If people didnt
discover/exploit new and better technology we'd still be counting grains of
sand on the beach. The abacus would be too high tech.
> In the SMTP example, you create a message in "your favorite editor". The
> message become an "object" which is dropped in the mailbox. The mailbox
Not really, the mail envelope would be dropped on the host it was destined to.
The object, envelope, would know how to get there, ie smtp.
I clarify this only because I am underwhelmed with the discussion my remarks
have generated to date and perhaps this my spur more (some) discussion. Perhaps
you all are too enamered(sic) with the latest goodies Johan has cooked up. A
pretty heady responsibility Jo, after all, they "love" you on Long Island.
Walt Corey - kz1f@kz1f.legent.com
----------------------------------
| |
| Space for Rent apply within |
| |
----------------------------------
------------------------------
Date: Wed, 20 Jan 93 22:13:50 MST
From: rnielsen@tapr.ampr.org (Bob Nielsen)
Subject: RCS
To: tcp-group@ucsd.edu
Really dumb question (RDQ) time.
What is RCS?
(In the DOS sense, not Radar Cross Section, with which I am quite
familiar.)
I thought I was fairly well up to speed on the path toward computer
literacy after 29 years of programming, but this is a new term to me!
Bob
Bob Nielsen W6SWE
ax.25: w6swe@wb7tpy.az.usa.na Internet: rnielsen@tapr.ampr.org
amateur IP: 44.124.12.16 CIS: 71540,2364
------------------------------
Date: Thu, 21 Jan 93 08:41:51 -0800
From: brian (Brian Kantor)
Subject: RCS
To: tcp-group
Well, it turns out I blew it; I saw those dozens of files in the rcs
directory and figured that Phil had just blown it, so I tar'd them up
into a single file.
I'll put them back the way he intended. Sorry.
- Brian
------------------------------
Date: Fri, 22 Jan 1993 00:21:10 +0100
From: Michael Kuch <mike@atlas.physchem.chemie.uni-tuebingen.de>
Subject: RCS
To: tcp-group@ucsd.edu
>
> Really dumb question (RDQ) time.
Nobody is perfect and nobody can know anithing :-)
>
> What is RCS?
RCS is a System for Version Conrol ("Revision Control System").
It's purpose is to keep software (source) systems consisting of many versions
and configurations well organized. It manages individual revision groups,
provides flexible selection functions for composing configurations, facilities
for merging updates with customer modifications, for distrinuted software
developement and for automatic identification ("stamping" of revisions and
configurations with unique markers). [Taken from the RCS-Intro by W. F. Tichy}
There are a few RCS's. One popular one in the UNIX-world is the GNU Revision
Controll System written by Walter F. Tichy. It consists of a set of UNIX
commands. I think it is also ported to DOS and OS/2. The DOS-Version can be
found on the SIMTEL mirror sites,
e.g. oak.oakland.edu:/pub/msdos/pgmutl/rcs56dos.zip
and the UNIX-Version on the mirror-sites of the GNU-Stuff,
e.g. ftp.informatik.tu-muenchen.de:/pub/GNU/rcs
(Current Version is 5.6, the DOS-Version is a port of the UNIX-Version).
Besides, the GNU Make supports the GNU RCS.
> [stuff deleted]
> Bob
>
> [sig deleted]
>
Michael Kuch
-------------------------------kuch@mailserv.zdv.uni-tuebingen.de
"listen: there's a hell of a good universe next door; let's go."
E.E. CUMMINGS 1894
------------------------------
Date: Thu, 21 Jan 1993 20:56:17 -0600
From: miltonm@inetnode.austin.ibm.com (Milton Miller)
Subject: RCS
To: rnielsen@tapr.ampr.org, tcp-group@ucsd.edu
RCS is Revision Control System, a set of source code control programs
that maintain versions of source files. Originally written for UNIX,
they have been ported to DOS.
milton
<I don't speak for IBM>
------------------------------
Date: Fri, 22 Jan 93 11:52:55 PST
From: "Jerzy Tarasiuk" <JT@zfja-gate.fuw.edu.pl>
Subject: RCS
To: rnielsen@tapr.ampr.org (Bob Nielsen)
> From: rnielsen@tapr.ampr.org (Bob Nielsen)
> Message-Id: <RDoPXB2w165w@tapr.ampr.org>
> Date: Wed, 20 Jan 93 22:13:50 MST
> Organization: Tucson Amateur Packet Radio
>
> Really dumb question (RDQ) time.
> What is RCS?
> (In the DOS sense, not Radar Cross Section, with which I am quite
> familiar.)
> I thought I was fairly well up to speed on the path toward computer
> literacy after 29 years of programming, but this is a new term to me!
It is Revision Control System and it is relatively new. Something
like CDC's MODIFY or UPDATE, CERN's PATCHY, IBM's UPDATE (on VM/CMS),
DEC's VAX/VMS CMS (Code Management System; I'am not sure if remember
it correctly), UNIX SCCS (Source Code Control System). All these are
(or were) used to maintain program sources (keep track on changes
made to these sources). Some people say RCS is the best.
Perhaps CDC's UPDATE or CERN's PATCHY are better, but they differ
a lot: they require user to enter changes rather than edit files.
RCS, SCCS and CMS allow user to get source file, edit it and put back;
at least DEC's CMS is multi-user (keeps inter-user interaction).
I know there are more similar systems in the world, bu don't know or
remember others; e.g. there is (or was to be) a system running on any
mainframe (e.g. IBM, VAX) with same full-screen menu on each :?-).
Designed for high-energy physics programs management to allow hundred
people in several contries to synchronize their work on program source.
73's, JT
------------------------------
Date: Thu, 21 Jan 93 17:06:31 EST
From: crompton@NADC.NADC.NAVY.MIL (D. Crompton)
Subject: TIP BBS
To: tcp-group@ucsd.edu
I am having much trouble with the NOS tip incoming modem connection
------------------------------
End of TCP-Group Digest V93 #22
******************************
******************************