HECnet

hecnet@lists.dfupdate.se

15589 discussions

by bqt＠softjar.se

On 2013-01-08 17:47, sampsa at mac.com wrote: On 7 Jan 2013, at 22:37, Johnny Billquist <bqt at softjar.se> wrote: It would. However, I don't expect us to run out of addresses any time soon. However, areas are a rather limited resource, and we are slowly running out of them. Sampsa, do you really think three areas are motivated? DECnet was not designed with the idea that physically separate places needed separate areas. Areas are more of a logicial division thing (although some constraints do exist on areas). I'll be happy to remumber should this happen... I'm still not getting why you need three areas. You have nowhere near 3000 nodes. In reality, even two areas are excessive. :-) Johnny

13 years, 1 month

Area 48.....

by sampsa＠mac.com

On 7 Jan 2013, at 22:37, Johnny Billquist <bqt at softjar.se> wrote: It would. However, I don't expect us to run out of addresses any time soon. However, areas are a rather limited resource, and we are slowly running out of them. Sampsa, do you really think three areas are motivated? DECnet was not designed with the idea that physically separate places needed separate areas. Areas are more of a logicial division thing (although some constraints do exist on areas). I'll be happy to remumber should this happen... sampsa

13 years, 1 month

subnet info, was Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by wonko＠4amlunch.net

On 1/8/2013 9:24 AM, Johnny Billquist wrote: Data mining is difficult, since there are different systems, with different possibilities of extracting it, and in different formats. Sampsa's goal here is mapping HECnet. My goal is to write a data mining service that just happens to provide the data that a mapper would use. To that end, I'll be stashing all this data in a database of some sort (details unknown as yet, see below) A centralized repository of data is nice in many ways, but it is a headache to manage. Absolutely it is, but if people are already putting INFO.TXT files out there they are doing 99% of the work already, we just need to get the data in a single place. That said, I could be convinced of setting something semi-automatic up. A reasonable way would be for people to give me machines to poll, and then I'd setup an automated process to poll those machines for files in a specific format. I can then create a database out of that, and make it available through the web, as well as over DECnet, and also as a summarized file. Anything would be pretty easy if we just have the data collected. I think this would be fantastic. I already have something of a start for this in the form of my database of nodes in HECnet. I'd need to extend it with more fields, but that would be pretty easy. It's all in Datatrieve today, and that should be accessible over DECnet right now (even though I seem to remember that VMS hosts had some problems with that). I'll have to learn how to access that db. I'm already extracting information from that database for the hecnet web-page on MIM (accessible as Madame). So, if we can just decide on what we want, and how to make the information available, I'll sit down and write the code to fix it. Do you want to also store my data or should I do that myself? I might do it myself at least for now until I know what exactly I need/want to save. -brian

13 years, 1 month

NCP-F-NETIO

by system＠TMESIS.COM

Brian Hechinger <wonko at 4amlunch.net> writes: On 1/8/2013 10:55 AM, Brian Schenkenberger, VAXman- wrote: > What version of VMS and how do you get back the NCP$_NETIO error? OpenVMS E8.4 on node RHESUS 8-JAN-2013 19:03:23.78 Uptime 8 04:55:33 If you get an actual text string back, you might try: > > "PIPE NCP TELL.... ; SHOW SYMBOL $STATUS" Oooh, that's nifty. I'll have to do that. I don't see why you can't just issue the NCL TELL from the command line > just once to get the failure results. Because the failure is transient. It's not happening 100% of the time. Fair 'nuff... Make certain you maintain space around the ';' or DCL parsing may think it's a file version separator. Since the ';' was already spoken for in VMS, applying unix pipeline syntax requires that spacing for the ';'. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

13 years, 1 month

NCP-F-NETIO

by wonko＠4amlunch.net

On 1/8/2013 10:55 AM, Brian Schenkenberger, VAXman- wrote: What version of VMS and how do you get back the NCP$_NETIO error? OpenVMS E8.4 on node RHESUS 8-JAN-2013 19:03:23.78 Uptime 8 04:55:33 If you get an actual text string back, you might try: "PIPE NCP TELL.... ; SHOW SYMBOL $STATUS" Oooh, that's nifty. I'll have to do that. I don't see why you can't just issue the NCL TELL from the command line just once to get the failure results. Because the failure is transient. It's not happening 100% of the time. -brian

13 years, 1 month

NCP-F-NETIO

by system＠TMESIS.COM

Brian Hechinger <wonko at 4amlunch.net> writes: On 1/7/2013 3:21 PM, Brian Schenkenberger, VAXman- wrote: > Can't you issue it from the command line? Python, if you are issuing the > command from os.system("TELL...") is probably just spawning off commands. > The context will be lost if that's the case. I'm using is.popen(), so yeah, i think i'm out of luck in that case. I'll just have to add some logic to maybe re-try the node if I get this. What version of VMS and how do you get back the NCP$_NETIO error? If you get an actual text string back, you might try: "PIPE NCP TELL.... ; SHOW SYMBOL $STATUS" I don't see why you can't just issue the NCL TELL from the command line just once to get the failure results. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

13 years, 1 month

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by wonko＠4amlunch.net

I'll send out a "let me know if you aren't showing up" email when i'm ready to tackle stuff that's being missed. Hang tight. :) -brian On 1/8/2013 9:47 AM, hvlems at zonnet.nl wrote: Area 44 is also missing. Anything I ought to have done? Hans -----Original Message----- From: Brian Hechinger <wonko at 4amlunch.net> Sender: owner-hecnet at Update.UU.SE Date: Tue, 08 Jan 2013 09:33:27 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SE Subject: Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H. On 1/7/2013 9:25 PM, Ian McLaughlin wrote: Sampsa, I appear to be missing. Are you able to add me? No, you are missing because you can't currently be found. We'll find you, be patient. :) My area router is A42RTR 42.1023. It is adjacent to SUN 52.1 and GW 61.1. Unfortunately for your scanning program, 42.1023 is a Cisco router. Yeah, Cisco routers have yet to be tackled. -brian

13 years, 1 month

NCP-F-NETIO

by wonko＠4amlunch.net

On 1/7/2013 3:21 PM, Brian Schenkenberger, VAXman- wrote: Can't you issue it from the command line? Python, if you are issuing the command from os.system("TELL...") is probably just spawning off commands. The context will be lost if that's the case. I'm using is.popen(), so yeah, i think i'm out of luck in that case. I'll just have to add some logic to maybe re-try the node if I get this. -brian

13 years, 1 month

PDP-11 OSes in SIMH

by wonko＠4amlunch.net

On 1/6/2013 8:04 PM, Clem Cole wrote: well the cluster stuff that TruCluster is based is already FOSS. checkout OpenSSI.org. sadly that tree is dead/or nearly so. Bruce stopped working on it and never was able to get the vproc layer into the Linux upstream sources. which is a real shame Oh, nice! Maybe we should get that somewhere else. Like NetBSD or rolled into the Illumos stuff. :) -brian

13 years, 1 month

_PROVISIONAL_ map of HECnet, courtesy largely of Brian H.

by hvlems＠zonnet.nl

Area 44 is also missing. Anything I ought to have done? Hans -----Original Message----- From: Brian Hechinger <wonko at 4amlunch.net> Sender: owner-hecnet at Update.UU.SE Date: Tue, 08 Jan 2013 09:33:27 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SE Subject: Re: [HECnet] _PROVISIONAL_ map of HECnet, courtesy largely of Brian H. On 1/7/2013 9:25 PM, Ian McLaughlin wrote: Sampsa, I appear to be missing. Are you able to add me? No, you are missing because you can't currently be found. We'll find you, be patient. :) My area router is A42RTR 42.1023. It is adjacent to SUN 52.1 and GW 61.1. Unfortunately for your scanning program, 42.1023 is a Cisco router. Yeah, Cisco routers have yet to be tackled. -brian

13 years, 1 month

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet