On Sat, 18 May 2013, H Vlems wrote:
A list of my systems:
44.1 HELIUM VAXstation 3100-M48 VMS 7.2
44.2 XENON VAXstation 4000-60 VMS 7.2
44.3 ARGON VAXstation 4000-90A VMS 7.3
44.4 NEON Asus Eee pc Fedora 14
44.5 ZILVER VAXstation 4000-60 VMS 7.3
44.6 JODIUM VAXstation 2000 VMS 5.5-1
44.7 RADON VAXstation 3100 VMS 5.5-1
44.8 ASTAAT DECserver 100
44.9 OSMIUM Digital Server 5305 5/533 VMS 8.3
44.10 CHLOOR VAXstation 4000-90A VMS 7.2
44.11 ZWAVEL microVAX 3100-10e VMS 6.1
44.12 INDIUM VXT2000+
44.13 ERBIUM AlphaServer 800 5/500 Tru64 5.0
44.14 BROOM AlpaServer 1200 5/400 VMS 7.3-2
44.15 FOSFOR VAXstation 4000-60 VMS 7.3
44.16 COBALT VAXstation 4000-60 VMS 7.3
44.17 KOPER VAXstation 2000 VMS 5.5-1
44.18 CERIUM VAX 4000-100A VMS 7.3
44.19 IJZER Compaq XP1000 6/500 VMS 8.3
44.20 CHROOM VAX 4000-100A VMS 7.3
44.21 NIKKEL VAXstation 4000-90A VMS 7.3
44.22 ZINK VAXstation 4000 VLC VMS 7.3
44.23 LOOD microVAX 3100-30 VMS 7.3
44.24 CURIUM Multia VX42 4/233 VMS 7.3
44.25 KWIK VAXstation 4000-60 VMS 7.3
44.26 AURUM Integrity rx2600 VMS 8.4
44.27 RADIUM HP dc5000 sff Windows XP
44.28 TIN AlphaServer 1200 5/533 VMS 8.3
44.29 FLUOR AlphaServer 1000A 5/333 VMS 7.3-2
44.30 BOOR VAXstation 4000-60 VMS 7.1
44.31 SELEEN microVAX 3100-20e VMS 6.1
44.32 ARSEEN microVAX 3100-20e VMS 6.1
44.33 CARBON DEC AXP 3000-300X VMS 1.5-1H1
44.34 OXYGEN DEC AXP 3000-300X VMS 6.1
44.35 TITAAN AlphaServer DS20E 6/666 VMS 8.3
44.36 URAAN AlphaServer 1000A 5/333 VMS 8.3
44.37 BARIUM AlphaServer 1200 5/533 VMS 8.3
44.38 CESIUM Digital Server 5305 5/533 VMS 8.3
44.39 KALIUM AlphaServer 300 Tru64 5.1a
44.40 SODIUM Digital Server 5305 5/533 VMS 8.3
44.41 AZOTE <not in use>
44.42 VISMUT AlphaServer 800 5/333 Tru64 5.1a
44.43 OZON AlphaServer DS10 6/466 VMS 8.4
44.1023 A44RTR simh VAXserver 3900 VMS 6.1
Now that's quite a few systems!
-----Oorspronkelijk bericht-----
Van: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] Namens
Sampsa Laine
Verzonden: zaterdag, mei 2013 16:00
Aan: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Another sillyness. More information in the nodename
database on MIM.
My boxes:
London based boxes:
8.401 CHIMPY: DS10, OpenVMS 8.3
8.400 GORVAX: SIMH, OpenVMS 7.3
8.403 RHESUS: rx2600, OpenVMS 8.4E (also offers a variety of services, see
http://rhesus.sampsa.com/)
47.100 HILANT Cluster in Hila, Finland, composed of:
47.556 KUHAVX SIMH running VMS 7.3
47.555 LABVAX - = -
47.727 SHAMS - = -
47.559 HPIVAX - = - (Raspberry Pi)
47.113 SIIRI MicroVAX 3400, VMS 7.3
47.700 K4VX1 VAXstation 4000/90, VMS 7.3
47.701 K4VX2 VAXstation 4000/60, VMS 7.3
On 17 May 2013, at 17:03, Johnny Billquist <bqt at softjar.se> wrote:
On 2013-05-17 16:18, Bob Armstrong 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.
Much of the information you want (all of it, I think) is already in the
INFO.TXT file -
$ type legato""::info.txt
....
ADDR |NAME |OWNER |EMAIL |HARDWARE
|OS
|LOCATION |NOTES
2.1 |LEGATO|Bob Armstrong |bob at
jfcl.com |simh
|OpenVMS
7.3|Milpitas, CA, US|DCN Multinet Ro
uter
2.2 |POCO | | |MicroVAX-2000
|
| |6MB, RD54, TK50
2.4 |MEZZO | | |PDP-11/53
|RSTS
| |3.5MB, 2xRA73,TK70, SCSI
2.6 |LARGO | | |VAX-11/730
|VMS 4.7
| |R80, 2xRA81, RL02, RX02, TU80
2.7 |CODA | | |DS20E
|OpenVMS
8.3| |
2.9 |DIVISI| | |VAX-8350
|VMS
5.5-2
| |16MB, RA81, RA82, TU81+
2.10 |ADAGIO| | |VAXserver 3900
|VMS 6.0
| |RA81, RX50, 2xRD54, Kennedy 9610, RRD50, RF31, 2xRF71,
RF72, SQ703, Exabyte 8505
2.11 |LENTO | | |PDP-11/73
|RSX-11M+
| |2xRD32, RX50, RL02, Kennedy 9600
2.12 |JENSEN| | |DEC 2000 axp
|OpenVMS
7.3| |
2.13 |ZITI | | |eBox-3310
|Ubuntu
| |
2.14 |MULTIA| | |Multia UDB
|OpenVMS
7.3| |
2.15 |PAVANE| | |DECstation 3100
|Ultrix
| |MIPS box w/DECnet-Ultrix
2.16 |SKETTI| | |HP ProLiant ML110G4
|Ubuntu
| |
2.18 |DSRVB1| | |DECserver-200/MC
|
| |
2.19 |DSRVB2| | |DECserver-200/MC
|
| |
FWIW, keeping a central database up to date is going to be a nightmare
-
that's why we invented the INFO.TXT files; so each sysadmin could locally
update his own information.
Yes. I know... :-)
Which I said this is all voluntary and so on. I've just felt that the
INFO.TXT is not really working that well either. At least not from my point
of view. I'm willing to try different things. I could consider some
automatic scraping and population of the nodename database from some
distributed sources as well, if we can come up with something that seems
reasonable.
Oh, and thanks.
Johnny
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments