On 2011-12-31 02.48, Steve Davidson wrote:
Johnny,
You are talking about the INFO.TXT file that is located in the default
DECnet directory.
Right. I even have one on MIM::
I just couldn't remember the name or format of the file, but figured someone else probably would. Little did I realized that others had already responded with the same information. :-)
The one "problem" with it, is that machines that aren't online also can't be queried for that file, so it might be a bit limited from that point of view.
Johnny
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 30, 2011 8:46 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Someone (I don't remember who) had a suggestion a year or two ago, that
machines should have a file in the default DECnet directory, with some
basic information about the node in a defined format, and the file with
a defined name, so that anyone could easily extract and figure out
information about atleast running nodes.
Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I
could of course take additional information as I'm already keeping a
nodename database in Datatrieve. No big deal to add additional
information if we'd like that... Then I can generate any kind of reports
based on this. As can others (if they can get remote Datatrieve to work
against RSX.)
Johnny
On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
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
On Dec 30, 2011, at 5:42, Johnny Billquist <bqt at softjar.se> wrote:
On 2011-12-30 02.44, Brian Hechinger wrote:
Agh, magica. Those were the good old days. :)
Magica is still around. I only wish I could turn her on more often. Cooling is the problem.
I really need to go dig my /70 out and start running it one of these days. That and my /34a. I don't currently have anywhere appropriate to run them, however. :(
Hum...? I think that it terminated on our VAX 8650.
That is the only thing I can remember on which I had serial ports to spare. Running Ultrix on the machine at the time.
Maybe that's it and I'm misremembering. I remember it ran Ultrix but remember it being MIPS for some reason.
That machine is also still around, but also powered off because of cooling. Big ECL machine. Lots of heat... But it's KRILLE (1.8).
It can boot VMS, Ultrix and NetBSD. Only got DECnet for VMS though.
Yeah, a shame it's too expensive to run. Nice machine.
-brian
Johnny,
You are talking about the INFO.TXT file that is located in the default
DECnet directory.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, December 30, 2011 8:46 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Re: Topology 28-Dec-2011
Someone (I don't remember who) had a suggestion a year or two ago, that
machines should have a file in the default DECnet directory, with some
basic information about the node in a defined format, and the file with
a defined name, so that anyone could easily extract and figure out
information about atleast running nodes.
Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I
could of course take additional information as I'm already keeping a
nodename database in Datatrieve. No big deal to add additional
information if we'd like that... Then I can generate any kind of reports
based on this. As can others (if they can get remote Datatrieve to work
against RSX.)
Johnny
On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
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
On 2011-12-30 17.28, Gregg Levine wrote:
Incidentally Johnny Billquist, have we ever worked out a reasonable
method of assigning a dynamic IP address to be reachable by the
efforts of the network? I know it works for websites.....
Uh? Not sure what you mean?
Johnny
Someone (I don't remember who) had a suggestion a year or two ago, that machines should have a file in the default DECnet directory, with some basic information about the node in a defined format, and the file with a defined name, so that anyone could easily extract and figure out information about atleast running nodes.
Maybe that idea could be expanded upon?
Seems very tedious for people to constantly mail updates... Although I could of course take additional information as I'm already keeping a nodename database in Datatrieve. No big deal to add additional information if we'd like that... Then I can generate any kind of reports based on this. As can others (if they can get remote Datatrieve to work against RSX.)
Johnny
On 2011-12-30 15.59, hvlems at zonnet.nl wrote:
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
So I was digging through the garage (we just moved and it is packed full of crap) and ran across the VAXstation 4000/90 so I pulled it out. I was very excited until I realized I had a problem. Mainly, no way to plug it into the network.
Crap, now where are my AUI transceivers buried?
I'll find one. I swear! :)
-brian
I think SLAVE::INFO.TXT is a fairly good example of the format.
Fortunately you appear to be using pretty much the same format as I am.
The good thing about standards is that there are so many to choose from
:-)
Bob
On Fri, 30 Dec 2011, Gregg Levine wrote:
reachable via the Internet via SSH and then VNC. The listing of who
and what regarding the attempted break-ins on the SSH port is
Speaking of SSH, for those that run Linux on the list and like to leave ssh open - I normally use public/private keys but I don't normally have my laptop or key-on-a-stick with me so I allow passwords as well on my home server. A little program called "sshdfilter" automatically watches logs (via a named pipe) and when someone comes knocking (or guesses a password wrong x times) it automatically firewalls the IP for a good long time. I use it on most any host I expose to the Internet with ssh.
Hopefully this isn't too offtopic ...
Fred
On 30/12/2011 16:15, Bob Armstrong wrote:
Bob describes the format in his version. I don't know how up-to-date it
is... Bob???
The format description is as current as any that I know about.
The actual data about my local machines is a little out of date, but the
syntax of the file is correct.
$ TYPE LEGATO::INFO.TXT
Bob
I think SLAVE::INFO.TXT is a fairly good example of the format.
Regards, Mark.
On Fri, Dec 30, 2011 at 8:05 AM, Fred <fcoffey at misernet.net> wrote:
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.
Hello!
I quite agree. On my resident Linux (Intel) platform here, who also
hosts my website, I would when vacation time loomed set it to be
reachable via the Internet via SSH and then VNC. The listing of who
and what regarding the attempted break-ins on the SSH port is
hilarious. It would be the classic dictionary attack at work. That's
the exact same one tried out on a VAX running BSD 4,2 all the way back
in 1987 (or so), the cuckoo's egg case at work.
Come to think of it I would also from time to time check his error and
access logs for the web serving functions. It's downright laughable
the preposterous efforts people would try that would cause anything
except Apache on Linux to stumble.
Incidentally Johnny Billquist, have we ever worked out a reasonable
method of assigning a dynamic IP address to be reachable by the
efforts of the network? I know it works for websites.....
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
