[Info-vax] Installing and using GNV - some feedback and questions

[Simon Clubley]

On 2016-10-23, John E. Malmberg <wb8tyw at qsl.net_work> wrote:
> On 10/22/2016 7:49 PM, Simon Clubley wrote:
>

[snip]

>> I also had to manually run the command procedures to create the aliases
>> for the commands; this was not done automatically as part of the PCSI
>> installation routine. If you are expected to do this manually, this
>> should be part of the release notes as well.
>
> The aliases should be created automatically.  This worked when I first 
> installed Bash on IA64 and on VAX, and works for all the upgrades so far.
>
> I did find that when installing over GNV kits, that the aliases did not 
> always get properly created on some systems.  I just did not have the 
> resources/time to find out why the procedure works the second time it is 
> run and not the first time.
>
> The various full GNV kits seem to have done different things as they 
> have been installed and updated the files, so it is hard to predict what 
> may or may not be present.
>
> The last full GNV kit that I installed was GNV 2.1.3 on Alpha.  I have 
> not tried installing the GNV 3.1 kits at all, so all GNV components on 
> my VAX and IA64 are from these kits.
>

First off, thanks for the detailed response and thanks for the work
you and others are doing on GNV.

It's become clear based on the other comments that the GNV base kit
provides some functionality infrastructure which I require so I'm going
to find some time in the future to remove the existing installation and
reinstall the updated kits on top of the GNV base kit.

You mention GNV 3.1 above but the latest I can find on SF is V3.0-1.

Is this the version you meant or is there a later version I am
unaware of ?

> Unfortunately I have not had time to get all the core kits building on 
> VAX.  The big issue is that Bash 4.3+ expects 64 bit ino_t structure and 
> DEC C/VAX does not support 64 bit integers.  I just have not taken the 
> time to work around all the VAX issues.  So the VAX kits are what I 
> could easily build.
>
>> Hitting Ctrl-C while running ls takes you back to DCL; you need to issue
>> the continue command from DCL to resume bash execution.
>
> That is a bug.  There are still some issues with Control-C/Y handling. 
> The major focus has been in getting Configure/Make scripts to run.
>

It's easy enough for me to type "c" and return when it happens... :-)

[snip]

Thanks once again,

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world