Christine Caulfield wrote:
On 21/10/09 10:22, Sampsa Laine wrote:
I'm starting to get concerned that HECnet is almost running TOO well,
i.e. there's not much left to tweak :)
Where should we go from here? Setting up our own virtual X.25 PSDN
tunnelled over IP maybe? Something crazy with SNA?
You could make the DECnet Linux tools with with RSX -- Johnny is always complaining they're broken (though they worked for me last I tried) :S
Maybe we should make some new tests. Whenever you have time... :-)
Johnny
On 21/10/09 10:34, Sampsa Laine wrote:
Btw, i think your info.txt is missing the header row as well as any data
for ROOSTA itself.
Ah sorry, I didn't realise the header was compulsory. I"m not sure where the info for ROOSTA went. I distinctly remember typing it in!
Then again, people keep hassling me at work this morning, so I probably typed it into an IRC window by mistake!
Chrissie
On 21 Oct 2009, at 10:31, Christine Caulfield wrote:
On 21/10/09 10:23, Sampsa Laine wrote:
Set that up before you joined HECnet I'm guessing, and forgot it was in
place when you did :)
Yes, it's acually an emergency disk image that I pressed into work
when my VAX got too noisy and the simh I used to use on OS/X was
broken by the Snow Leopard update.
I dread to think what else might be on it ...
Chrissie
On 21 Oct 2009, at 10:21, Christine Caulfield wrote:
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
Btw, i think your info.txt is missing the header row as well as any data for ROOSTA itself.
Sampsa
On 21 Oct 2009, at 10:31, Christine Caulfield wrote:
On 21/10/09 10:23, Sampsa Laine wrote:
Set that up before you joined HECnet I'm guessing, and forgot it was in
place when you did :)
Yes, it's acually an emergency disk image that I pressed into work when my VAX got too noisy and the simh I used to use on OS/X was broken by the Snow Leopard update.
I dread to think what else might be on it ...
Chrissie
On 21 Oct 2009, at 10:21, Christine Caulfield wrote:
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 10:23, Sampsa Laine wrote:
Set that up before you joined HECnet I'm guessing, and forgot it was in
place when you did :)
Yes, it's acually an emergency disk image that I pressed into work when my VAX got too noisy and the simh I used to use on OS/X was broken by the Snow Leopard update.
I dread to think what else might be on it ...
Chrissie
On 21 Oct 2009, at 10:21, Christine Caulfield wrote:
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 10:22, Sampsa Laine wrote:
I'm starting to get concerned that HECnet is almost running TOO well,
i.e. there's not much left to tweak :)
Where should we go from here? Setting up our own virtual X.25 PSDN
tunnelled over IP maybe? Something crazy with SNA?
You could make the DECnet Linux tools with with RSX -- Johnny is always complaining they're broken (though they worked for me last I tried) :S
Chrissie
Sampsa Laine wrote:
I'm starting to get concerned that HECnet is almost running TOO well, i.e. there's not much left to tweak :)
Where should we go from here? Setting up our own virtual X.25 PSDN tunnelled over IP maybe? Something crazy with SNA?
HECnet have been running fine for a long, long time by now. :-)
But there are definitely things to look at.
Ideally if would be very nice to implement an alternative to my bridge program which actually routes instead of bridging. But that would take a lot of work, and I definitely don't have time for that right now.
Ideally it should also be able to talk with the Cisco implementation in this case.
And of course, people could think about writing bridge programs for things like PHONE <-> talk, ftp gateways, and other stuff, if they feel like getting a project. There is much to play around with.
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
Set that up before you joined HECnet I'm guessing, and forgot it was in place when you did :)
Sampsa
On 21 Oct 2009, at 10:21, Christine Caulfield wrote:
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 10:07, Sampsa Laine wrote:
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA
from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
Eek!
I had *::* */def
I have now removed it!
Chrissie
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
Does ROOSTA have a proxy setup for the SYSTEM user? When I DIR ROOSTA from RHESUS (as SYSTEM), I seem to get your SYS$MANAGER: directory....
On 21 Oct 2009, at 10:05, Christine Caulfield wrote:
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
On 21/10/09 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.
I've added an INFO.TXT to ROOSTA
Chrissie
