Date: Thu, 3 Jun 93 04:30:02 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 #143
To: tcp-group-digest
TCP-Group Digest Thu, 3 Jun 93 Volume 93 : Issue 143
Today's Topics:
Hints for Getting & Compiling NOS base code
In-Reply-To: Software-2000 demise? (3 msgs)
IP address starting with digits ??? (4 msgs)
New WAMPES version
NLIST format
PMNOS with cross connections. (3 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: Wed, 2 Jun 1993 07:21:09 -0700 (PDT)
From: "Erik Olson" <erik@marge.phys.washington.edu>
Subject: Hints for Getting & Compiling NOS base code
To: TCP-Group@UCSD.Edu
>>A much easier way is:
>>
>> for %a in (*.c) do co %a
>>
>>at the DOS prompt.
>>
>When I got home, I tried this and found that it don't work, SORRY!!
>But this does.
> cd \nos\rcs
> for %a in (*.*) do echo >> ..\cox.bat co %a
> cd ..
> cox
Actually, just looking at the first one should be obvious it won't actually
work; I thought the author was just being pedagogic. Here's what I did:
for %a in (RCS\*.*) do co %a
Which DOES work. Now, is this a feature in DOS 5 or above, or have I always
missed the "for" command?
- Erik
---
erik@marge.phys.washington.edu Erik Olson, at home
------------------------------
Date: Wed, 2 Jun 93 06:30:26 MDT
From: "Karl Larsen" <klarsen@centaur.arl.army.mil>
Subject: In-Reply-To: Software-2000 demise?
To: tcp-group@ucsd.edu
> Organization: Grendel's Lair
> To: tcp-digest@UCSD.EDU
> Subject: Software-2000 demise?
>
> It appears the people supporting Net/Rom have once again died.
> Originally Amatech in Clovis Calif. it had moved to Fresno with
> another person supporting it. That seems to have fallen off the
> face of the earth now as well. Mail to Ron Raikes WA8DED either
> at Compuserve or Packet BBS goes unanswered. I guess if this
> keeps up, then TheNet and G8BPQ will be the "standard" by which
> others should comply.
Ron Raikes with some reason is sour on netrom. He invented it
and a German group NORD-LINK copied it, according to Ron. Now
TheNet is being improved on by Bill Beech, NJ7P. You may have seen
the version 2.06, which is my favorite.
>
> Has anyone out there had contact with any of the above recently?
> 73 es GA from Jeff
> GRNDEL:WA6FWI-9 and WHTIER:WA6FWI-2 apparently fatherless children now.
> --
> J. Angus: jangus@skyld.tele.com -- "Als ik Kan", Gustav Stickley
> US Mail: PO Box 4425 Carson, CA 90749-4425 1 (310) 324-6080
NJ7P is re-writing the 1985 version of netrom specifications.
He is almost complete and it will be made public soon. The purpose
is to have a recient document for present day writers of ham code.
If you MUST do something NOW, get the 1985 specifications
from ucsd.edu, where else?
73, de karl
_________________________________________
| Internet klarsen@centaur.arl.army.mil |
| Fido 1:381/401 |
| k5di@k5di.nm.usa.na |
| Ham IP 44.30.2.5 |
| (505) 678-3145 weekdays 524-3303 home |
|________________________________________|
------------------------------
Date: Wed, 2 Jun 93 06:30:26 MDT
From: "Karl Larsen" <klarsen@centaur.arl.army.mil>
Subject: In-Reply-To: Software-2000 demise?
To: tcp-group@ucsd.edu
> Organization: Grendel's Lair
> To: tcp-digest@UCSD.EDU
> Subject: Software-2000 demise?
>
> It appears the people supporting Net/Rom have once again died.
> Originally Amatech in Clovis Calif. it had moved to Fresno with
> another person supporting it. That seems to have fallen off the
> face of the earth now as well. Mail to Ron Raikes WA8DED either
> at Compuserve or Packet BBS goes unanswered. I guess if this
> keeps up, then TheNet and G8BPQ will be the "standard" by which
> others should comply.
Ron Raikes with some reason is sour on netrom. He invented it
and a German group NORD-LINK copied it, according to Ron. Now
TheNet is being improved on by Bill Beech, NJ7P. You may have seen
the version 2.06, which is my favorite.
>
> Has anyone out there had contact with any of the above recently?
> 73 es GA from Jeff
> GRNDEL:WA6FWI-9 and WHTIER:WA6FWI-2 apparently fatherless children now.
> --
> J. Angus: jangus@skyld.tele.com -- "Als ik Kan", Gustav Stickley
> US Mail: PO Box 4425 Carson, CA 90749-4425 1 (310) 324-6080
NJ7P is re-writing the 1985 version of netrom specifications.
He is almost complete and it will be made public soon. The purpose
is to have a recient document for present day writers of ham code.
If you MUST do something NOW, get the 1985 specifications
from ucsd.edu, where else?
73, de karl
_________________________________________
| Internet klarsen@centaur.arl.army.mil |
| Fido 1:381/401 |
| k5di@k5di.nm.usa.na |
| Ham IP 44.30.2.5 |
| (505) 678-3145 weekdays 524-3303 home |
|________________________________________|
------------------------------
Date: Wed, 2 Jun 93 06:30:26 MDT
From: "Karl Larsen" <klarsen@centaur.arl.army.mil>
Subject: In-Reply-To: Software-2000 demise?
To: tcp-group@ucsd.edu
> Organization: Grendel's Lair
> To: tcp-digest@UCSD.EDU
> Subject: Software-2000 demise?
>
> It appears the people supporting Net/Rom have once again died.
> Originally Amatech in Clovis Calif. it had moved to Fresno with
> another person supporting it. That seems to have fallen off the
> face of the earth now as well. Mail to Ron Raikes WA8DED either
> at Compuserve or Packet BBS goes unanswered. I guess if this
> keeps up, then TheNet and G8BPQ will be the "standard" by which
> others should comply.
Ron Raikes with some reason is sour on netrom. He invented it
and a German group NORD-LINK copied it, according to Ron. Now
TheNet is being improved on by Bill Beech, NJ7P. You may have seen
the version 2.06, which is my favorite.
>
> Has anyone out there had contact with any of the above recently?
> 73 es GA from Jeff
> GRNDEL:WA6FWI-9 and WHTIER:WA6FWI-2 apparently fatherless children now.
> --
> J. Angus: jangus@skyld.tele.com -- "Als ik Kan", Gustav Stickley
> US Mail: PO Box 4425 Carson, CA 90749-4425 1 (310) 324-6080
NJ7P is re-writing the 1985 version of netrom specifications.
He is almost complete and it will be made public soon. The purpose
is to have a recient document for present day writers of ham code.
If you MUST do something NOW, get the 1985 specifications
from ucsd.edu, where else?
73, de karl
_________________________________________
| Internet klarsen@centaur.arl.army.mil |
| Fido 1:381/401 |
| k5di@k5di.nm.usa.na |
| Ham IP 44.30.2.5 |
| (505) 678-3145 weekdays 524-3303 home |
|________________________________________|
------------------------------
Date: 2 Jun 93 12:24:50 GMT
From: Jon Jagger <J.R.Jagger@sheffield-hallam.ac.uk>
Subject: IP address starting with digits ???
To: tcp-group@ucsd.edu
Hi there,
I was wondering about UK Novice callsigns. e.g., 2e1bsd.
The IP address for these seem to 'default' to e.g., 2e1bsd.ampr.org.
I seem to remember that IP addresses starting with a
digit is a NO NO. Can anyone tell me which RFC I need
to look in to confirm/deny my failing memory.
Thanks
JJ
:: Jon Jagger J.R.Jagger@shu.ac.uk
:: Sheffield Hallam University, Pond Street, SHEFFIELD S1 1WB
:: Tel 0742 533802/432889 (work/home) Fax 0743 533840
:: Newspaper ad: Men wanted for expanding contracting company!
------------------------------
Date: Wed, 2 Jun 1993 09:59:43 -0600 (CDT)
From: lcz@dptspd.sat.datapoint.com (Lee Ziegenhals)
Subject: IP address starting with digits ???
To: tcp-group@ucsd.edu
>I seem to remember that IP addresses starting with a
>digit is a NO NO. Can anyone tell me which RFC I need
>to look in to confirm/deny my failing memory.
I just checked RFC1123, "Requirements for Internet Hosts -- Application and
Support". Paragraph 2.1 changes the original requirement (in RFC952) to
allow the first character of a host name to be either a letter or a digit.
It is a "must-implement" requirement, so the names you mentioned should
work fine.
73/Lee, N5LYT
------------------------------
Date: Wed, 2 Jun 1993 09:59:43 -0600 (CDT)
From: lcz@dptspd.sat.datapoint.com (Lee Ziegenhals)
Subject: IP address starting with digits ???
To: tcp-group@ucsd.edu
>I seem to remember that IP addresses starting with a
>digit is a NO NO. Can anyone tell me which RFC I need
>to look in to confirm/deny my failing memory.
I just checked RFC1123, "Requirements for Internet Hosts -- Application and
Support". Paragraph 2.1 changes the original requirement (in RFC952) to
allow the first character of a host name to be either a letter or a digit.
It is a "must-implement" requirement, so the names you mentioned should
work fine.
73/Lee, N5LYT
------------------------------
Date: Wed, 2 Jun 1993 10:13:47 -0500
From: miltonm@inetnode.austin.ibm.com (Milton Miller)
Subject: IP address starting with digits ???
To: J.R.Jagger@sheffield-hallam.ac.uk
I believe the updated rule is that no part of the hostname should be
completely numeric. I thought I saw this in the host requirements
rfc's, but can't find it on a quick search :-)
Some resolvers may still have trouble with leading digits;
NOS is not among those.
milton
--
Milton Miller KB5TKF
miltonm@austin.ibm.com miltonm@inetnode.austin.ibm.com
Since I am not a spokesman, these views are independant of any IBM may have.
------------------------------
Date: Wed, 02 Jun 1993 11:25:42 -0700
From: Paul Traina <pst@cisco.com>
Subject: New WAMPES version
To: deyke@hpfcmdd.fc.hp.com
Just FYI, I've done a WAMPES port for A/UX 3.0, but it still has some
bugs in it.
Right now, cnet is non-functional, and telneting into the system
properly does the utmp/passwd/login stuff, but data is never passed
back to the net program.
------------------------------
Date: Wed, 02 Jun 93 09:34:55 EST
From: lshannon@wpdsmtp.daytonoh.ncr.com
Subject: NLIST format
To: TCP-Group@ucsd.edu
>Does anyone have a hack to make the FTP NLIST format compatible
>with UNIX SVR4? Many of the new windows IP clients try to
>interpret the format to provide point-and-click directory
>switching and file selection. The WNOS formatted display is
>different than any of the more widely known formats supported by
>these packages (e.g. QVTNET, SuperTCP, Pathway Access,...).
>
>Thanks, Lew, K0RR
What I need is a diff to the jnos (not WNOS) FTP server that
formats the NLIST response in a compatible manner.
Thanks,
Lew K0RR
------------------------------
Date: Wed, 2 Jun 93 14:13:21 EDT
From: RWAUSTIN@ATLVM1.VNET.IBM.COM
Subject: PMNOS with cross connections.
To: TCP-Group@UCSD.Edu
I am using pmnos with two ports defined. one radio and one slip phone
link. the lines work just fine seperately. However, I am not able to dial
in on the slip link, and then command NOS to connect/telnet to a station
that I am able to get on the radio link. If someone has this operational
I would appreciate a copy of the autoexec file.
another note. If a user 'ttylinks' to my station the connection is
established, but immmediately is closed. any hints on this one?
Otherwise, PMNOS is doing a super job of nos for me on my os/2 systems
the PMAIL screens are great also. Many thanks to Walt. I am looking
forward to his new version.
73,
=> Bob - N4CLH @ WA4BRO.ATL.GA.USA.NA
=> amprnet - 44.36.0.120 (n4clh.ampr.org) Atlanta, GA.
=> internet - rwaustin@atlvm1.vnet.ibm.com
------------------------------
Date: Wed, 2 Jun 93 14:13:21 EDT
From: RWAUSTIN@ATLVM1.VNET.IBM.COM
Subject: PMNOS with cross connections.
To: TCP-Group@UCSD.Edu
I am using pmnos with two ports defined. one radio and one slip phone
link. the lines work just fine seperately. However, I am not able to dial
in on the slip link, and then command NOS to connect/telnet to a station
that I am able to get on the radio link. If someone has this operational
I would appreciate a copy of the autoexec file.
another note. If a user 'ttylinks' to my station the connection is
established, but immmediately is closed. any hints on this one?
Otherwise, PMNOS is doing a super job of nos for me on my os/2 systems
the PMAIL screens are great also. Many thanks to Walt. I am looking
forward to his new version.
73,
=> Bob - N4CLH @ WA4BRO.ATL.GA.USA.NA
=> amprnet - 44.36.0.120 (n4clh.ampr.org) Atlanta, GA.
=> internet - rwaustin@atlvm1.vnet.ibm.com
------------------------------
Date: Wed, 2 Jun 93 14:13:21 EDT
From: RWAUSTIN@ATLVM1.VNET.IBM.COM
Subject: PMNOS with cross connections.
To: TCP-Group@UCSD.Edu
I am using pmnos with two ports defined. one radio and one slip phone
link. the lines work just fine seperately. However, I am not able to dial
in on the slip link, and then command NOS to connect/telnet to a station
that I am able to get on the radio link. If someone has this operational
I would appreciate a copy of the autoexec file.
another note. If a user 'ttylinks' to my station the connection is
established, but immmediately is closed. any hints on this one?
Otherwise, PMNOS is doing a super job of nos for me on my os/2 systems
the PMAIL screens are great also. Many thanks to Walt. I am looking
forward to his new version.
73,
=> Bob - N4CLH @ WA4BRO.ATL.GA.USA.NA
=> amprnet - 44.36.0.120 (n4clh.ampr.org) Atlanta, GA.
=> internet - rwaustin@atlvm1.vnet.ibm.com
------------------------------
End of TCP-Group Digest V93 #143
******************************
******************************