HECnet September 2008

hecnet@lists.dfupdate.se

10 participants
44 discussions

by bqt＠softjar.se

Christine Caulfield wrote: I'm going to be a pest now, sorry. My old node ZAPHOD died over a year ago. However I now have a new node so I'm reusing the name. This next bit might sound slightly anal but bear with me. The old Zaphod was an Alpha so it had a node number 3.33. The new one is a macmini running Linux (and I hope to replace fentib) so has a node number of 3.55. My numbering scheme (as if you cared) goes 01-19 PCs 20-30 hmm, I forget now. I'm sure I had some once though. 30-39 DEC systems 40-49 HP systems 50-59 Apple systems 60-69 Sun systems So, anyway the point is that can you please renumber ZAPHOD from 3.33 to 3.55. Sorry. No problemo. :-) I've done it on MIM now. Johnny

15 years, 7 months

SMG bug correction for VAX V7.2 and others

by gerry77＠mail.com

I think I've found a solution for the infamous SMG bug on releases for which actually HP does not (still) provide a patch: I've discovered that the official published patch for OpenVMS VAX V7.3 works apparently flawlessy even on V7.2 and maybe also on older releases like V7.1 and so on. Obviously it cannot be installed via VMSINSTAL because the kit does check for the correct version and release, but it's always possibile to extract the new SMGSHR.EXE file from the kit and put it in place. To be safe, I've copied it to the specific portion of my system root (e.g. DKA0:[SYS0.SYSLIB]) instead of the better common one, but I do not have a cluster and SYS$SHARE does point to both locations, so I've achieved the same result. After that I've just typed INSTALL REPLACE SYS$SHARE:SMGSHR.EXE/OPEN/HEADER/SHARED and that's it! I've done the same for my OpenVMS Alpha V7.2 system by using the V7.3-2 patch, but in that case a newer release is temporarily needed to extract SMGSHR.EXE from the PCSI kit because it's in the new compressed form that's not supported by V7.2 (I do not know when it was introduced, I used a V8.2 to extract). In the next few days, if I'll see that everything works without any problems, maybe I'll rename the original SMGSHR.EXE file and replace it with the new one so to have just one of it and in the right place. Hope this helps! G.

15 years, 7 months

Node rename

by christine.caulfield＠googlemail.com

I'm going to be a pest now, sorry. My old node ZAPHOD died over a year ago. However I now have a new node so I'm reusing the name. This next bit might sound slightly anal but bear with me. The old Zaphod was an Alpha so it had a node number 3.33. The new one is a macmini running Linux (and I hope to replace fentib) so has a node number of 3.55. My numbering scheme (as if you cared) goes 01-19 PCs 20-30 hmm, I forget now. I'm sure I had some once though. 30-39 DEC systems 40-49 HP systems 50-59 Apple systems 60-69 Sun systems So, anyway the point is that can you please renumber ZAPHOD from 3.33 to 3.55. Sorry. -- Chrissie

15 years, 7 months

dnprogs 2.46 for Linux released (NEW FEATURES!)

by christine.caulfield＠googlemail.com

I'm very pleased to announce the new dnprogs release. With not one, not two, but FOUR new programs - you lucky people :-) The first two were contributed by Philipp 'ph3-der-loewe' Schafft and consist of two command-line utilities: dnetstat is a version of netstat for DECnet, it reformats the /proc file output in a more user-friendly manner. dnetcat is a DECnet version of netcat, an invaluable utility for all network nerds. Philipp has offered to update the wiki to show how to use this utility to run SSH over DECnet! And finally, I have also been busy. I have done something I said I'd write years ago and that's an Network Management Listener program. Yes, finally you can go into NCP on a VMS or RSX system (yes, I tested it on RSX, thanks Johnny) and type in "TELL LINUX SHOW ADJACENT NODES". It only supports a subset of commands at the moment, but I will probably add more. It currently will do: SHOW/LIST KNOWN NODES SHOW ADJACENT NODES SHOW EXEC CHAR To make this work you'll need to add a new line to dnetd.conf - see the sample file shipped with the package for the details. There's also a client side version of that, well partly. dncopynodes allows a Linux user to pull a node list off a remote VMS or RSX system and build up a full decnet.conf file. It will fill in the current exec details too so that the file it generates can simply be copied to /etc. WARNING ... DO NOT do 'dncopynodes > /etc/decnet.conf' as it will overwrite the file before it gets a chance to use it to make the initial connection! http://sourceforge.net/project/showfiles.php?group_id=4993&package_id=5032&… -- Chrissie

15 years, 8 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet September 2008