HECnet December 2012

hecnet@lists.dfupdate.se

43 participants
1079 discussions

INFO.TXT, was Re: [HECnet] UPDATE: HECNET.HLP file for VMS systems

by bqt＠softjar.se

On 2012-12-31 08:08, sampsa at mac.com wrote: Funny thing about LEGATO's INFO.TXT - my parser looks for the .BEGIN-HECNET-INFO tag and deletes all text after that. I should probably make a manual HLP file for LEGATO, Bob you OK with that? LEGATO's INFO.TXT have real yucky file attributes and a real yucky file format. :-) (What on earth was used to produce it???) Directory LEGATO::SYS$SPECIFIC:[FAL$SERVER] 31-DEC-12 13:59:07 INFO.TXT;1 Size: 8./35. Created: 08-JUL-10 10:54:52 Owner: [000376,000373] Revised: 27-DEC-12 19:24:34(6.) Expires: <none_specified> File protection: System:RE, Owner:RE, Group:RE, World:RE File organization: Sequential File attributes: Allocation=0 Record format: Stream-CR, no maximum defined Record attributes: Carriage return What does it mean if you have stream-CR and attribute Carriage Return? I mean, yes, each record is separated by a CR, and then what? Add an additional CR at the end of each line? Also, if I pull the file down to MIM, it gets really strange. Dumping the file, there aren't a single CR in the file. Each line is terminated by a LF, so it looks really Unixy. Not sure if something mangled the file during the transfer maybe, or does it look that way on a VMS system too? Johnny sampsa On 30 Dec 2012, at 21:22, Dave McGuire <mcguire at neurotica.com> wrote: On 12/29/2012 09:28 PM, Dennis Boone wrote: So what's supposed to be in this INFO.TXT file that everyone's been talking about lately? I think I may be too much of a newcomer here to know about it. Where should it be, and what should it contain? Bob has a nice explanation in his INFO.TXT file on LEGATO. Got it...Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 4 months

New nodes..

by sampsa＠mac.com

Johnny, Can you register these for me when you get a moment: BEIRUT 8.220 LBNVAX 8.221 KIBBEH 8.222 sampsa

11 years, 4 months

INFO.TXT, was Re: [HECnet] UPDATE: HECNET.HLP file for VMS systems

by sampsa＠mac.com

Funny thing about LEGATO's INFO.TXT - my parser looks for the .BEGIN-HECNET-INFO tag and deletes all text after that. I should probably make a manual HLP file for LEGATO, Bob you OK with that? sampsa On 30 Dec 2012, at 21:22, Dave McGuire <mcguire at neurotica.com> wrote: On 12/29/2012 09:28 PM, Dennis Boone wrote: So what's supposed to be in this INFO.TXT file that everyone's been talking about lately? I think I may be too much of a newcomer here to know about it. Where should it be, and what should it contain? Bob has a nice explanation in his INFO.TXT file on LEGATO. Got it...Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA

11 years, 4 months

Known areas as seen from MIM::

by gregg.drwho8＠gmail.com

On Sun, Dec 30, 2012 at 10:51 PM, <sampsa at mac.com> wrote: On SAMPSACOM london, I name my machines after monkeys: CHIMPY:: RHESUS:: GORVAX:: (Gorilla VAX, SIMH that runs on a OS X box called Gorilla) SAMPSACOM Finland is a bit more all over the place :) sampsa On 31 Dec 2012, at 05:03, Cory Smelosky <b4 at gewt.net> wrote: On 30 Dec 2012, at 22:01, "Steve Davidson" <jeep at scshome.net> wrote: If you mean SGC, and SG1 that is simple! The code name for VMS was STAR. With the exception of the STRGTE:: (Stargate) cluster (SGC, SG1, SG2,...SGn) all VMS nodes are named after stars. The PDP-11 nodes are usually named after planets (if they were available). That IS quite simple and straightforward! It's also less limited than my naming scheme. ;) SGC is Stargate Command (STRGTE:: cluster boot node) SG1 is Stargate 1, and is the primary "gateway" to the rest of HECnet for the Eastern US (application server). SG2 is Stargate 2, and is the primary "gateway" to another network (application server). SG3 is Stargate 3, and is the primary "gateway" to... (application server). That definitely makes sense. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:46 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known areas as seen from MIM:: On 28 Dec 2012, at 23:42, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:40 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known nodes as seen from MIM:: On 28 Dec 2012, at 23:37, "Steve Davidson" <jeep at scshome.net> wrote: SG1$$ ncp NCP>tell mim show known area Known Area Volatile Summary as of 28-DEC-2012 23:33:58 Area State Circuit Next node to area 1 reachable 1.13 (MIM) 2 reachable UNA-0 2.1 (LEGATO) 3 reachable UNA-0 19.41 (SG1) 4 reachable UNA-0 4.248 (SIMVAX) 5 reachable UNA-0 5.1023 (A5RTR) 6 reachable UNA-0 6.1 (STAR69) 7 reachable UNA-0 8.400 (GORVAX) 8 reachable UNA-0 8.400 (GORVAX) 9 reachable UNA-0 19.41 (SG1) 11 reachable UNA-0 11.2 (MAISA) 12 reachable UNA-0 12.2 (BENDER) 18 reachable UNA-0 2.1 (LEGATO) 19 reachable UNA-0 19.41 (SG1) 20 reachable UNA-0 19.41 (SG1) 28 reachable UNA-0 28.41 (RULLFS) 33 reachable UNA-0 19.41 (SG1) 42 reachable UNA-0 19.41 (SG1) 44 reachable UNA-0 44.21 (NIKKEL) 47 reachable UNA-0 47.556 (KUHAVX) 51 reachable UNA-0 2.1 (LEGATO) 52 reachable UNA-0 19.41 (SG1) 59 reachable UNA-0 19.41 (SG1) 61 reachable UNA-0 19.41 (SG1) 62 reachable UNA-0 62.637 (CTAKAH) NCP> -Steve I see a lot of these are routed via SG1. ;) -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. That is the whole purpose of SG1::. Route... Route... Route... That is all it does :-) Now if only I could completely figure out your naming scheme. ;) What's it's highest uptime? -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. Hello! Sampsa that does explain it. You do know why the favorite OS for X86 machines makes a funny noise and moves in colonies? Think hard, it is a well dressed bird who's biggest problem is people. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

11 years, 4 months

INFO.TXT, was Re: [HECnet] UPDATE: HECNET.HLP file for VMS systems

by gregg.drwho8＠gmail.com

On Sun, Dec 30, 2012 at 2:22 PM, Dave McGuire <mcguire at neurotica.com> wrote: On 12/29/2012 09:28 PM, Dennis Boone wrote: So what's supposed to be in this INFO.TXT file that everyone's been talking about lately? I think I may be too much of a newcomer here to know about it. Where should it be, and what should it contain? Bob has a nice explanation in his INFO.TXT file on LEGATO. Got it...Thanks! -Dave -- Dave McGuire, AK4HZ New Kensington, PA Hello! No you've got a fellow named Monty Python (all of them) plus a heap big snake. -- ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

11 years, 4 months

Known areas as seen from MIM::

by sampsa＠mac.com

On SAMPSACOM london, I name my machines after monkeys: CHIMPY:: RHESUS:: GORVAX:: (Gorilla VAX, SIMH that runs on a OS X box called Gorilla) SAMPSACOM Finland is a bit more all over the place :) sampsa On 31 Dec 2012, at 05:03, Cory Smelosky <b4 at gewt.net> wrote: On 30 Dec 2012, at 22:01, "Steve Davidson" <jeep at scshome.net> wrote: If you mean SGC, and SG1 that is simple! The code name for VMS was STAR. With the exception of the STRGTE:: (Stargate) cluster (SGC, SG1, SG2,...SGn) all VMS nodes are named after stars. The PDP-11 nodes are usually named after planets (if they were available). That IS quite simple and straightforward! It's also less limited than my naming scheme. ;) SGC is Stargate Command (STRGTE:: cluster boot node) SG1 is Stargate 1, and is the primary "gateway" to the rest of HECnet for the Eastern US (application server). SG2 is Stargate 2, and is the primary "gateway" to another network (application server). SG3 is Stargate 3, and is the primary "gateway" to... (application server). That definitely makes sense. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:46 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known areas as seen from MIM:: On 28 Dec 2012, at 23:42, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:40 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known nodes as seen from MIM:: On 28 Dec 2012, at 23:37, "Steve Davidson" <jeep at scshome.net> wrote: SG1$$ ncp NCP>tell mim show known area Known Area Volatile Summary as of 28-DEC-2012 23:33:58 Area State Circuit Next node to area 1 reachable 1.13 (MIM) 2 reachable UNA-0 2.1 (LEGATO) 3 reachable UNA-0 19.41 (SG1) 4 reachable UNA-0 4.248 (SIMVAX) 5 reachable UNA-0 5.1023 (A5RTR) 6 reachable UNA-0 6.1 (STAR69) 7 reachable UNA-0 8.400 (GORVAX) 8 reachable UNA-0 8.400 (GORVAX) 9 reachable UNA-0 19.41 (SG1) 11 reachable UNA-0 11.2 (MAISA) 12 reachable UNA-0 12.2 (BENDER) 18 reachable UNA-0 2.1 (LEGATO) 19 reachable UNA-0 19.41 (SG1) 20 reachable UNA-0 19.41 (SG1) 28 reachable UNA-0 28.41 (RULLFS) 33 reachable UNA-0 19.41 (SG1) 42 reachable UNA-0 19.41 (SG1) 44 reachable UNA-0 44.21 (NIKKEL) 47 reachable UNA-0 47.556 (KUHAVX) 51 reachable UNA-0 2.1 (LEGATO) 52 reachable UNA-0 19.41 (SG1) 59 reachable UNA-0 19.41 (SG1) 61 reachable UNA-0 19.41 (SG1) 62 reachable UNA-0 62.637 (CTAKAH) NCP> -Steve I see a lot of these are routed via SG1. ;) -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. That is the whole purpose of SG1::. Route... Route... Route... That is all it does :-) Now if only I could completely figure out your naming scheme. ;) What's it's highest uptime? -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

11 years, 4 months

Known areas as seen from MIM::

by b4＠gewt.net

On 30 Dec 2012, at 22:01, "Steve Davidson" <jeep at scshome.net> wrote: If you mean SGC, and SG1 that is simple! The code name for VMS was STAR. With the exception of the STRGTE:: (Stargate) cluster (SGC, SG1, SG2,...SGn) all VMS nodes are named after stars. The PDP-11 nodes are usually named after planets (if they were available). That IS quite simple and straightforward! It's also less limited than my naming scheme. ;) SGC is Stargate Command (STRGTE:: cluster boot node) SG1 is Stargate 1, and is the primary "gateway" to the rest of HECnet for the Eastern US (application server). SG2 is Stargate 2, and is the primary "gateway" to another network (application server). SG3 is Stargate 3, and is the primary "gateway" to... (application server). That definitely makes sense. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:46 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known areas as seen from MIM:: On 28 Dec 2012, at 23:42, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:40 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known nodes as seen from MIM:: On 28 Dec 2012, at 23:37, "Steve Davidson" <jeep at scshome.net> wrote: SG1$$ ncp NCP>tell mim show known area Known Area Volatile Summary as of 28-DEC-2012 23:33:58 Area State Circuit Next node to area 1 reachable 1.13 (MIM) 2 reachable UNA-0 2.1 (LEGATO) 3 reachable UNA-0 19.41 (SG1) 4 reachable UNA-0 4.248 (SIMVAX) 5 reachable UNA-0 5.1023 (A5RTR) 6 reachable UNA-0 6.1 (STAR69) 7 reachable UNA-0 8.400 (GORVAX) 8 reachable UNA-0 8.400 (GORVAX) 9 reachable UNA-0 19.41 (SG1) 11 reachable UNA-0 11.2 (MAISA) 12 reachable UNA-0 12.2 (BENDER) 18 reachable UNA-0 2.1 (LEGATO) 19 reachable UNA-0 19.41 (SG1) 20 reachable UNA-0 19.41 (SG1) 28 reachable UNA-0 28.41 (RULLFS) 33 reachable UNA-0 19.41 (SG1) 42 reachable UNA-0 19.41 (SG1) 44 reachable UNA-0 44.21 (NIKKEL) 47 reachable UNA-0 47.556 (KUHAVX) 51 reachable UNA-0 2.1 (LEGATO) 52 reachable UNA-0 19.41 (SG1) 59 reachable UNA-0 19.41 (SG1) 61 reachable UNA-0 19.41 (SG1) 62 reachable UNA-0 62.637 (CTAKAH) NCP> -Steve I see a lot of these are routed via SG1. ;) -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. That is the whole purpose of SG1::. Route... Route... Route... That is all it does :-) Now if only I could completely figure out your naming scheme. ;) What's it's highest uptime? -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

11 years, 4 months

Known areas as seen from MIM::

by jeep＠scshome.net

If you mean SGC, and SG1 that is simple! The code name for VMS was STAR. With the exception of the STRGTE:: (Stargate) cluster (SGC, SG1, SG2,...SGn) all VMS nodes are named after stars. The PDP-11 nodes are usually named after planets (if they were available). SGC is Stargate Command (STRGTE:: cluster boot node) SG1 is Stargate 1, and is the primary "gateway" to the rest of HECnet for the Eastern US (application server). SG2 is Stargate 2, and is the primary "gateway" to another network (application server). SG3 is Stargate 3, and is the primary "gateway" to... (application server). -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:46 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known areas as seen from MIM:: On 28 Dec 2012, at 23:42, "Steve Davidson" <jeep at scshome.net> wrote: -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Cory Smelosky Sent: Friday, December 28, 2012 23:40 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Known nodes as seen from MIM:: On 28 Dec 2012, at 23:37, "Steve Davidson" <jeep at scshome.net> wrote: SG1$$ ncp NCP>tell mim show known area Known Area Volatile Summary as of 28-DEC-2012 23:33:58 Area State Circuit Next node to area 1 reachable 1.13 (MIM) 2 reachable UNA-0 2.1 (LEGATO) 3 reachable UNA-0 19.41 (SG1) 4 reachable UNA-0 4.248 (SIMVAX) 5 reachable UNA-0 5.1023 (A5RTR) 6 reachable UNA-0 6.1 (STAR69) 7 reachable UNA-0 8.400 (GORVAX) 8 reachable UNA-0 8.400 (GORVAX) 9 reachable UNA-0 19.41 (SG1) 11 reachable UNA-0 11.2 (MAISA) 12 reachable UNA-0 12.2 (BENDER) 18 reachable UNA-0 2.1 (LEGATO) 19 reachable UNA-0 19.41 (SG1) 20 reachable UNA-0 19.41 (SG1) 28 reachable UNA-0 28.41 (RULLFS) 33 reachable UNA-0 19.41 (SG1) 42 reachable UNA-0 19.41 (SG1) 44 reachable UNA-0 44.21 (NIKKEL) 47 reachable UNA-0 47.556 (KUHAVX) 51 reachable UNA-0 2.1 (LEGATO) 52 reachable UNA-0 19.41 (SG1) 59 reachable UNA-0 19.41 (SG1) 61 reachable UNA-0 19.41 (SG1) 62 reachable UNA-0 62.637 (CTAKAH) NCP> -Steve I see a lot of these are routed via SG1. ;) -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. That is the whole purpose of SG1::. Route... Route... Route... That is all it does :-) Now if only I could completely figure out your naming scheme. ;) What's it's highest uptime? -Steve -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

11 years, 4 months

"Hacking" attempts

by b4＠gewt.net

On 30 Dec 2012, at 21:22, Oleg Safiullin <form at pdp-11.org.ru> wrote: Cory Smelosky wrote: On 29 Dec 2012, at 16:51, Oleg Safiullin <form at pdp-11.org.ru> wrote: I know someone that was trying to make an IRC bot in x86 ASM... I'll probably do one in PDP-11 assembler, just to spite you. :-) Hehe. I ported unix `cal' program from OpenBSD sources to RSX, wrote it in MACRO-11, and got an interesting result: Have a copy of it laying around? http://pdp-11.org.ru/files/rsx-11/cal0100.zip Thanks -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

11 years, 4 months

"Hacking" attempts

by form＠pdp-11.org.ru

Cory Smelosky wrote: On 29 Dec 2012, at 16:51, Oleg Safiullin <form at pdp-11.org.ru> wrote: I know someone that was trying to make an IRC bot in x86 ASM... I'll probably do one in PDP-11 assembler, just to spite you. :-) Hehe. I ported unix `cal' program from OpenBSD sources to RSX, wrote it in MACRO-11, and got an interesting result: Have a copy of it laying around? http://pdp-11.org.ru/files/rsx-11/cal0100.zip

11 years, 4 months

← Newer
1
...
4
5
6
7
8
9
10
...
108
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet December 2012