And in non VMSnet speak?
It works for Sampsa - it must not like you, Peter :-)
Access information for node CODA::/ACCOUNT:decnet
I don't think "decnet" is the correct account to use for default access -
it should be a null account name and a null password. In transparent DECnet
speak, it would be CODA""::INFO.TXT. I don't know exactly how that
translates to NFT.
Bob
Ok....
NFT>type CODA::INFO.TXT
BOB AND DEBEE'S COMPUTER GARAGE
-------------------------------
This is the node CODA, currently an AlphaServer DS20E running OVMS 8.3, in
Bob and Debee's Computer Garage and Retirement Home for old DEC computers.
It normally runs 24x7 and serves as our server for mail, DNS, NTP, Samba, and
a few other services. It's also a hub of sorts for other machines which connect
to HECnet via Multinet DECnet over TCP/IP connections.
Thanks..
I know, I was kidding - sorry...:)
On 21 Oct 2009, at 00:53, Peter Lothberg wrote:
http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=coda
Yes... But we want this to work on HECnet, right.. Need some help
here, as I knew nothing about VMS... And VMS assumes the other side is
a VMS box..
-P
:-P
On 21 Oct 2009, at 00:48, Peter Lothberg wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a
machine
readable section at the end that contains information about the
local nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight,
counting mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
NFT>print CODA::INFO.TXT
Access information for node CODA::/ACCOUNT:decnet
User: decnet
Password:
?Remote node refused connection - Access not permitted
NFT>
And in non VMSnet speak?
-P
http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=coda
Yes... But we want this to work on HECnet, right.. Need some help
here, as I knew nothing about VMS... And VMS assumes the other side is
a VMS box..
-P
:-P
On 21 Oct 2009, at 00:48, Peter Lothberg wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a
machine
readable section at the end that contains information about the
local nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight,
counting mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
NFT>print CODA::INFO.TXT
Access information for node CODA::/ACCOUNT:decnet
User: decnet
Password:
?Remote node refused connection - Access not permitted
NFT>
And in non VMSnet speak?
-P
And in non VMSnet speak?
It works for Sampsa - it must not like you, Peter :-)
Access information for node CODA::/ACCOUNT:decnet
I don't think "decnet" is the correct account to use for default access -
it should be a null account name and a null password. In transparent DECnet
speak, it would be CODA""::INFO.TXT. I don't know exactly how that
translates to NFT.
Bob
http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=coda
:-P
On 21 Oct 2009, at 00:48, Peter Lothberg wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
NFT>print CODA::INFO.TXT
Access information for node CODA::/ACCOUNT:decnet
User: decnet
Password:
?Remote node refused connection - Access not permitted
NFT>
And in non VMSnet speak?
-P
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
NFT>print CODA::INFO.TXT
Access information for node CODA::/ACCOUNT:decnet
User: decnet
Password:
?Remote node refused connection - Access not permitted
NFT>
And in non VMSnet speak?
-P
I've updated CHIMPY in the same format.
Sampsa
On 21 Oct 2009, at 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine
readable section at the end that contains information about the local nodes.
I already wrote a little DCL script that crawls the HECnet and collects all
the INFO.TXT files that it can find (so far there are eight, counting mine)
and if enough people adopt this format I'll write another little script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
