HECnet May 2013

hecnet@lists.dfupdate.se

38 participants
680 discussions

Another sillyness. More information in the nodename database on MIM.

by Paul_Koning＠Dell.com

On May 16, 2013, at 3:21 PM, Johnny Billquist wrote: On 2013-05-16 21:19, Paul_Koning at Dell.com wrote: My nodes: 9.54 (PYTHON) DECnet/Python router 9.55 (NI1D) DECnet/E, RSTS/E V10.1 on simh Cool. I didn't even know you had come online. I'll add these right away. Thanks. 9.55 only occasionally, but as soon as I get to the point in believing in 9.54 being stable when talking to Hecnet, I plan to leave it running routinely. paul

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by bqt＠softjar.se

On 2013-05-16 21:19, Paul_Koning at Dell.com wrote: My nodes: 9.54 (PYTHON) DECnet/Python router 9.55 (NI1D) DECnet/E, RSTS/E V10.1 on simh Cool. I didn't even know you had come online. I'll add these right away. Thanks. Johnny

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by Paul_Koning＠Dell.com

My nodes: 9.54 (PYTHON) DECnet/Python router 9.55 (NI1D) DECnet/E, RSTS/E V10.1 on simh paul

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by bqt＠softjar.se

On 2013-05-16 21:09, Ian McLaughlin wrote: Did I break it? File "US:[DECNET]HECNET.IDX" in incompatible use by another user File open failed, domain not readied Execution failed Field "HECNET" is undefined or used out of context Field "CURRENT" is undefined or used out of context My fault. I probably had the file opened non-shared from Datatrieve. Should be good now. Johnny Ian On 2013-05-16, at 12:06 PM, Johnny Billquist <bqt at softjar.se> wrote: On 2013-05-16 20:30, Johnny Billquist wrote: On 2013-05-16 18:28, Johnny Billquist wrote: This is a totally volontary thing. I've finally come to the point where I think that there are a few more pieces of data on nodes that would be nice/useful to have from time to time. So I've extended the nodename database on MIM for this. The fields that I have added are CPU, OS and location. You can see an example of values by going to http://madame.update.uu.se/~bqt/hecnet?node=mim So, feel free to submit data to me for nodes you know. Or look up information. Or suggest interfaces that you'd like to get to extract this information, and I'll try and comply. :-) Being border, I actually created a simple web page for it now. http://madame.update.uu.se/~bqt/nodedb Bored... I meant to say bored. Interesting mistype... Hmm... :-) Johnny --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=C371BD28BE5B11E2A…

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by ian＠platinum.net

Did I break it? File "US:[DECNET]HECNET.IDX" in incompatible use by another user File open failed, domain not readied Execution failed Field "HECNET" is undefined or used out of context Field "CURRENT" is undefined or used out of context Ian On 2013-05-16, at 12:06 PM, Johnny Billquist <bqt at softjar.se> wrote: On 2013-05-16 20:30, Johnny Billquist wrote: On 2013-05-16 18:28, Johnny Billquist wrote: This is a totally volontary thing. I've finally come to the point where I think that there are a few more pieces of data on nodes that would be nice/useful to have from time to time. So I've extended the nodename database on MIM for this. The fields that I have added are CPU, OS and location. You can see an example of values by going to http://madame.update.uu.se/~bqt/hecnet?node=mim So, feel free to submit data to me for nodes you know. Or look up information. Or suggest interfaces that you'd like to get to extract this information, and I'll try and comply. :-) Being border, I actually created a simple web page for it now. http://madame.update.uu.se/~bqt/nodedb Bored... I meant to say bored. Interesting mistype... Hmm... :-) Johnny --- Filter service subscribers can train this email as spam or not-spam here: http://my.email-as.net/spamham/cgi-bin/learn.pl?messageid=C371BD28BE5B11E2A…

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by bqt＠softjar.se

On 2013-05-16 20:30, Johnny Billquist wrote: On 2013-05-16 18:28, Johnny Billquist wrote: This is a totally volontary thing. I've finally come to the point where I think that there are a few more pieces of data on nodes that would be nice/useful to have from time to time. So I've extended the nodename database on MIM for this. The fields that I have added are CPU, OS and location. You can see an example of values by going to http://madame.update.uu.se/~bqt/hecnet?node=mim So, feel free to submit data to me for nodes you know. Or look up information. Or suggest interfaces that you'd like to get to extract this information, and I'll try and comply. :-) Being border, I actually created a simple web page for it now. http://madame.update.uu.se/~bqt/nodedb Bored... I meant to say bored. Interesting mistype... Hmm... :-) Johnny

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by bqt＠softjar.se

On 2013-05-16 18:28, Johnny Billquist wrote: This is a totally volontary thing. I've finally come to the point where I think that there are a few more pieces of data on nodes that would be nice/useful to have from time to time. So I've extended the nodename database on MIM for this. The fields that I have added are CPU, OS and location. You can see an example of values by going to http://madame.update.uu.se/~bqt/hecnet?node=mim So, feel free to submit data to me for nodes you know. Or look up information. Or suggest interfaces that you'd like to get to extract this information, and I'll try and comply. :-) Being border, I actually created a simple web page for it now. http://madame.update.uu.se/~bqt/nodedb Johnny

11 years, 6 months

Another sillyness. More information in the nodename database on MIM.

by bqt＠softjar.se

This is a totally volontary thing. I've finally come to the point where I think that there are a few more pieces of data on nodes that would be nice/useful to have from time to time. So I've extended the nodename database on MIM for this. The fields that I have added are CPU, OS and location. You can see an example of values by going to http://madame.update.uu.se/~bqt/hecnet?node=mim So, feel free to submit data to me for nodes you know. Or look up information. Or suggest interfaces that you'd like to get to extract this information, and I'll try and comply. :-) Johnny

11 years, 6 months

DECserver software collection

by bqt＠softjar.se

On 2013-05-15 00:42, G. wrote: Hi all, once upon a time (!) I collected whatever DECserver software I was able to find, thinking it would be eventually useful sometime into the future. Now I see on this mailing list some messages about DECserver software, so I thought about sharing whatever I know and have, to help others running their DECservers and maybe to increase my collection too. Here is what I have: MNENG1.SYS V1.1C BL46-13 MNENG1_A.SYS V1.1C BL46A-13 From Digital? MNENG2.SYS V2.0 BL10D-40 MNENG2_DNPG.SYS V2.4 BL50 Copyright Digital Networks, DNPG, LLC MNENG3_DNPG.SYS V2.4 BL50 Copyright Digital Networks, DNPG, LLC PS0801ENG.SYS V2.0 BL23 PR0801ENG.SYS V3.3A BL40 DP0601ENG.SYS V2.0 BL29-04 SH1601ENG.SYS V2.2C BL46-13 WWENG1.SYS V1.1C BL46-13 WWENG2.SYS V2.0 BL10D-40 And this is what I miss (both from Digital): MNENG3.SYS MNENG4.SYS Finally, these should be the corresponding DECserver hardware devices: DECserver 90L+ PROM-based, no firmware DECserver 90TL MNENG1.SYS or MNENG2.SYS DECserver 90M (1MB mem) MNENG2.SYS DECserver 90M (2MB mem) MNENG3.SYS DECserver 90M+ (4MB mem) MNENG4.SYS DECserver 100 PS0801ENG.SYS DECserver 200 PR0801ENG.SYS DECserver 250 DP0601ENG.SYS DECserver 300 SH1601ENG.SYS DECserver 700 (1MB mem) WWENG1.SYS DECserver 700 (2MB mem) WWENG2.SYS DECserver 900TM WWENG2.SYS So, MNENG4.SYS seems to be the most important miss in my collection... Thanks to everyone, :) G. P.S. If you see anything wrong, let me know! :) Thanks. That was a great summary. We should just make them all available on HECnet as well. Care to send me copies? Or do someone already have all of them available? Like I said before, a few of them are already on MIM. Johnny

11 years, 6 months

HECnet LAT groups...

by bqt＠softjar.se

Hi. I'd like to ask people to look over their LAT setups. Looking at group 0 right now, the list is rather long, and containing lots of services that looks like they really would be better placed in some other group. The idea of group 0 has been to have publicly available systems in group 0, so that people using DECservers can just look at group 0, and whatever local groups they have, and not have a long list of services that are of no relevance at all to them. Johnny

11 years, 6 months

← Newer
1
...
34
35
36
37
38
39
40
...
68
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet May 2013