Yup, I stand corrected. Use a comma instead since my default csv separator is a semicolon.
------Origineel bericht------
Van: Bob Armstrong
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: RE: [HECnet] Re: Topology 28-Dec-2011
Verzonden: 30 december 2011 16:03
<address>-<name>-<hardware>-<os name>
Um, don't most hardware names contain dashes? VAX-11/730, PDP-11/70,
VAX-8350, ... ?
Or are you looking for something more basic - VAX, PDP, PC, ??
Bob
The INFO.TXT files in the default DECnet directories already give this information. An agreed apon format has already been established. Can you make use of that?
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl
Sent: Friday, December 30, 2011 9:59 AM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
<address>-<name>-<hardware>-<os name>
Um, don't most hardware names contain dashes? VAX-11/730, PDP-11/70,
VAX-8350, ... ?
Or are you looking for something more basic - VAX, PDP, PC, ??
Bob
Rok, the spreadsheet that I distributed also has a sheet called 'hosts'.
I'm willing to expand that list though I have the basty feeling it's going to take a lot more time than the project itself.
The information is not readily available thru NCP. Possibly NCL has a relevant command but if so my ncl is *very* rusty and it seems I'm pretty much the only phase V owner.
NCP gives limited information: the set exec node and sho exec (char) commands only tell you the os name. For vms it tells you what platform.
The excel file contains this information for each node in a single cell:
<address>-<name>-<hardware>-<os name>
Mark the hyphens: that way I can manipulate the csv file easily on vms with f$element ;-)
So anyone who mails me node data in the format listed gets data included in the file. What do you think?
Hans
-----Original Message-----
From: Rok Vidmar <rok.vidmar at gmail.com>
Sender: owner-hecnet at Update.UU.SE
Date: Fri, 30 Dec 2011 15:40:56
To: <hecnet at update.uu.se>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Re: Topology 28-Dec-2011
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
I can add whatever interesting information and I can add any number of
editors.
Once upon a time I tried to keep a list of the HECnet nodes - there's a
copy, albeit somewhat out of date, here-
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
feel free to copy whatever data from that one that you want.
FWIW, you're probably at least the third person to attempt an inventory of
HECnet, but don't let that discourage you :-)
Bob
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Well, both. I generated list of active nodes and I believe it will not be too
hard to manually update it from time to time.
I can add whatever interesting information and I can add any number of
editors. Any volunteers? Hans?
--
Regards, Rok
This should round out the map for area 19.
Rok -
Sorry, I'm confused. Is it your plan to keep a manually updated list of
all of HECnet? Are you looking for data on all known nodes, even end nodes
and ones that don't normally run 24x7? And how much data do you want for
each node? OS? Hardware type? Geographic location?
That's fine with me and I'm not complaining in the least if that's the
case! OTOH, I thought you were making a list of the active routing nodes,
which is an entirely different matter.
Bob
Rok,
PLUTO:: (19.23) DECnet/E 4.1 is up. MARS:: (19.84) is a mess and I don't have a workable RSX-11M-PLUS distribution to fix it so I think it is a complete loss. SIGH...
The STARS:: VAXcluster (19.77) and hopefully the GALAXY:: VMScluster (19.150) will be up either this evening or tomorrow.
This should round out the map for area 19.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Rok Vidmar
Sent: Friday, December 30, 2011 6:16 AM
To: hecnet at update.uu.se
Subject: [HECnet] Re: Topology 28-Dec-2011
Step closer to CSV:
Have a peek:
<https://docs.google.com/spreadsheet/ccc?key=0AmeaHhGPxCnRdFpmdXhhcG1YODd1UW…>
--
Regards, Rok
On Fri, 30 Dec 2011, Johnny Billquist wrote:
I'm still looking for script kiddies trying to hack MIM. Once in a while I do get people who try to login repeatedly as root, falken, and other known Unix accounts. Poor kids... ;-)
I'm glad I'm not the only one!
I leave telnet open on one of my VMS hosts and love looking at the audit logs. Most of the time folks just disconnect without even trying a username. Other times it is "Administrator" and their ilk ... Once or twice a month I'll read the logs and just laugh. You'd have to know me pretty well to guess the password for the few accounts on the system, I change them every 90, and of course intrusion detection is going to get you long before you get close. :)
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
