[Dropping some names off the distribution as similar information has
been sent to them]
John E. Malmberg wrote:
Craig A. Berry wrote:
On Apr 10, 2009, at 4:20 PM, Michael G Schwern wrote:
GNV should not be assigning that logical name and later versions than
the one they've got there don't. It should be safe just to deassign it.
$ @gnv$gnu:[lib]gnv_setup.com
$ show log bin
"BIN" = "GNV$GNU:[BIN]" (LNM$PROCESS_TABLE)
$ deassign bin
$ sh log bin
%SHOW-S-NOTRAN, no translation for logical name BIN
I was not aware of a later version than what I put on Encompasserve.
While I submitted the code to the maintainer for rebuilding the kit, I
had not heard of any new releases.
Encompasserve.org is running GNV 2.1-2 + patches that have been
submitted to HP. The GNV kit at the HP web site is still 2.1-2.
The version of GNV on Encompasserve puts the BIN logical in the process
table instead of the system table as the HP version did at the time I
installed it, so deassigning it to run Perl is the thing to do.
I just did a quick check. With out the logical name BIN defined there
are a number of things that will not work. This is because with out
that logical name, the CRTL redirects "/bin" to be "/SYS$SYSTEM"
Everything has to be relinked with a variant of the lib$initialize code
that I added to GNU TAR 1.19 in order to fix that.
Once we can get the patches that I submitted to Perl in place, I plan to
start looking at GIT, curl, and fixing up GNV. I just have not had as
much time to do this as I use to.
There is a porting_to_vms notes conference on Encompasserve.org where
anyone who wants to help can join in.
Regards,
-John
wb8...@qsl.net
Personal Opinion Only
