HECnet

hecnet@lists.dfupdate.se

7 participants
15595 discussions

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."

13 years, 2 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."

13 years, 2 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.

13 years, 2 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.

13 years, 2 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.

13 years, 2 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.

13 years, 2 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

13 years, 2 months

"Hacking" attempts

by mcguire＠neurotica.com

On 12/30/2012 09:19 PM, Cory Smelosky wrote: To be fair, PDP-11 assembler is...well, nice. I wonder how fat it'd be on an ungainly old x86. Modern or older x86? ;) There's a difference? I mean, I know a handful of instructions were stapled onto the side occasionally throughout the years, and x86_64 made things a BIT more sane...brought it squarely into the late 1980s...but it's still pretty ungainly. I was referring to something like: original 8086 ASM compared with late-model pentium III ASM. ;) Ahhh. In that case, not a whole lot of difference for app-level stuff. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years, 2 months

"Hacking" attempts

by b4＠gewt.net

On 30 Dec 2012, at 21:16, Dave McGuire <mcguire at neurotica.com> wrote: On 12/29/2012 04:59 PM, Cory Smelosky wrote: I ported unix `cal' program from OpenBSD sources to RSX, wrote it in MACRO-11, and got an interesting result: OpenBSD's cal.c - 562 lines My CAL.MAC - 490 lines :) That was... unexpected... :-) To be fair, PDP-11 assembler is...well, nice. I wonder how fat it'd be on an ungainly old x86. Modern or older x86? ;) There's a difference? I mean, I know a handful of instructions were stapled onto the side occasionally throughout the years, and x86_64 made things a BIT more sane...brought it squarely into the late 1980s...but it's still pretty ungainly. I was referring to something like: original 8086 ASM compared with late-model pentium III ASM. ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

13 years, 2 months

"Hacking" attempts

by mcguire＠neurotica.com

On 12/29/2012 04:59 PM, Cory Smelosky wrote: I ported unix `cal' program from OpenBSD sources to RSX, wrote it in MACRO-11, and got an interesting result: OpenBSD's cal.c - 562 lines My CAL.MAC - 490 lines :) That was... unexpected... :-) To be fair, PDP-11 assembler is...well, nice. I wonder how fat it'd be on an ungainly old x86. Modern or older x86? ;) There's a difference? I mean, I know a handful of instructions were stapled onto the side occasionally throughout the years, and x86_64 made things a BIT more sane...brought it squarely into the late 1980s...but it's still pretty ungainly. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

13 years, 2 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet