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
Bob asked me to supply this information - if there are any other lists
out there that need to be updated, please do so.
1.250,ORAC,Mark Wickens,mark at wickensonline.co.uk,VAXstation
4000/90,OpenVMS VAX 7.3,Windermere UK,
1.251,ZX6000,Mark Wickens,mark at wickensonline.co.uk,ZX6000,OpenVMS IA64
8.3.1-H1,Windermere UK,
1.252,NODE3,Mark Wickens,mark at wickensonline.co.uk,DEC 3000/600 AXP,
Digital Unix 4.0,Windermere UK
1.253,NODE2,Mark Wickens,mark at wickensonline.co.uk,DS10L,OpenVMS Alpha
8.3
1.254,ZEN,Mark Wickens,mark at wickensonline.co.uk,VAXstation 4000/90
1.255,X60,Mark Wickens,mark at wickensonline.co.uk,IBM X60 Thinkpad,Ubuntu
1.256,BUBBLE,Mark Wickens,mark at wickensonline.co.uk,VAXstation
4000/VLC,OpenVMS VAX 7.3,Windermere UK
Cheers, Mark.
On Tue, 2009-10-20 at 12:07 -0700, Bob Armstrong wrote:
Easiest for me (at least at this moment) would be for you to send me a few
comma separated lines in this format -
Address,Name,Owner,eMail,Hardware,OS,Location,Notes
Thanks,
Bob
-----Original Message-----
From: Mark Wickens [mailto:mark at wickensonline.co.uk]
Sent: Tuesday, October 20, 2009 12:03 PM
To: bob at jfcl.com
Subject: RE: hecnet email
On Tue, 2009-10-20 at 11:54 -0700, Bob Armstrong wrote:
Done.
BTW, are all those 1.25? nodes yours? FWIW - I don't think any of them
are on my node list...
Bob
-----Original Message-----
From: Mark Wickens [mailto:mark at wickensonline.co.uk]
Sent: Tuesday, October 20, 2009 11:39 AM
To: Bob Armstrong
Subject: hecnet email
Bob, can you update your decnet node list - my system bubble is fairly
new and I got a message bounce because of this.
Regards, Mark.
Yes they are - if you need any more information let me know - I can
either add an info.txt file or just send you some info directly
Regards Mark.
--
Mark -
You can put in an MX record for *.mail11.hecnet.eu that points to
mail.jfcl.com if you want. I have no objection, but if you do be sure to
let me know so that I can configure my SMTP server to accept mail for that
domain (otherwise you'll get "550 Relay not allowed...").
If you want to host my DCN Node List on that site it'd be nice. Just give
me a place to put it and a way to upload updates.
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Mark Wickens
Sent: Tuesday, October 20, 2009 11:42 AM
To: hecnet at Update.UU.SE
Subject: [HECnet] Domain registration hecnet.eu
Guys,
I've just registered hecnet.eu - should be sorted within 24 hours.
So, if we can agree amongst ourselves the best way forward with a mail
gateway then I can point mail.hecnet.eu (or some variant) to the
designated gateway.
I'm going to create a website under www.hecnet.eu - this will be a
community effort between us all I'm anticipating, so how would you like
to go forward - it'll be hosted on the newly acquired vaxstation
4000/VLC under WASD ideally, and what I'd like to do is open it up so
that people can edit files directly via hecnet to add their bit. Is that
an agreeable course of action?
Regards, Mark.
--
Suggestion: If we include external IP addresses for any nodes that have them in those data files we discussed yesterday, could we populate the DNS with these (i.e. chimpy.hecnet.eu points at CHIMPY's external IP address)?
Sampsa
On 20 Oct 2009, at 19:42, Mark Wickens wrote:
Guys,
I've just registered hecnet.eu - should be sorted within 24 hours.
So, if we can agree amongst ourselves the best way forward with a mail
gateway then I can point mail.hecnet.eu (or some variant) to the
designated gateway.
I'm going to create a website under www.hecnet.eu - this will be a
community effort between us all I'm anticipating, so how would you like
to go forward - it'll be hosted on the newly acquired vaxstation
4000/VLC under WASD ideally, and what I'd like to do is open it up so
that people can edit files directly via hecnet to add their bit. Is that
an agreeable course of action?
Regards, Mark.
--
DNS wasn't my problem, I do resolve to the new address. But it still
cannot be telneted to. Unreachable. I suspect a routing issue on the
remote side, if in fact TINA is up.
-Mark
Pontus Pihlgren wrote:
On Mon, Oct 19, 2009 at 03:16:27PM -0400, Mark Abene wrote:
While we're on the subject, PAMINA is unreachable via telnet, and I
haven't been able to telnet into TINA in almost 2 weeks. Any idea
what's been happening at update? I miss TINA's othello. :)
TINA has moved to 130.238.12.208 (from 130.238.8.42). The DNS entries
should be updated by now. I guess Bj rn forgon to tell hecnet at update :)
/Pontus
Thanks,
Mark
Johnny Billquist wrote:
Oh, you want updates? :-)
Let's see...
FNATTE have been decomissioned for good, I think.
PONDUS is now an 11/93 with 4 MB.
PAMINA is also KLH-10
Johnny
Bob Armstrong wrote:
Where is PDXVAX still noted as a 4000/VLC?
Well, on my list for one.
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Nobody sent me any corrections ...
Bob
