The following GNV utilities have been observed to exhibit behavior that varies from their UNIX counterparts.

• tar (this runs the OpenVMS utility VMSTAR, which differs slightly from the the genuine UNIX tar utility. Try gnutar instead.)
• vi (this runs a vi emulator based on the OpenVMS utility TPU, which differs slightly from the genuine UNIX vi utility)
• The intent of GNV is that all utilities accept UNIX-style file specifications (that is, those specifications containing slashes "/", single or double dots ".", "..", and so forth.) Several utilities included with GNV were ported to OpenVMS previously and can accept OpenVMS-style file specifications. In fact, some may not accept UNIX-style file specifications, such as the following:
  • unzip

This section provides directions for installing GNV onto your OpenVMS system. The latest GNV software is included in [GNV.KIT] on the Open Source Tools CD-ROM. You can also downline load the GNV software from either of the following locations:

http://h71000.www7.hp.com/OPENSOURCE/opensource.html

or

http://gnv.sourceforge.net.

9.1 Installing the GNV Software on Your System Disk

To install the GNV software on your system disk, follow these steps:

1. Load the installation kit media onto an available drive.
2. Log in to the SYSTEM account (at the login prompt, enter user name SYSTEM and the appropriate password), or an account with equivalent privileges.
3. At the DCL prompt ($), type the following command, as shown, where device-name is the name of the device containing the kit (a CD-ROM drive).

   $ PRODUCT INSTALL GNV /SOURCE=device-name:[GNV.KIT]

   
   To install your GNV software on a location other than the system disk, see Section 9.2.

4. When you enter the PRODUCT INSTALL command, the system responds with a display similar to the following:

   The following product has been selected: DEC AXPVMS GNV V2.1 Layered Product Do you want to continue? [YES]

   
   Continue the procedure by pressing the Enter key for the default (YES). The system responds as shown in the example below. The procedure might take several minutes and numerous messages might be displayed on the screen. In response to each prompt displayed by the system, choose the default answer.

   Configuration phase starting . . .: You will be asked to choose options, if any, for each selected product and for any products that may be installed to satisfy software dependency requirements. DEC AXPVMS GNV V2.1 Do you want the defaults for all options? [YES]

   
   Note that the only option with GNV is whether to include the source files with the installation. The default is YES.

5. Accept the default for all options by pressing the ENTER key. The system responds by asking whether you want to review all the options:

   Do you want to review the options? [NO]

6. Proceed with the GNV installation by pressing the ENTER key to accept the default (NO, skip review of options). The installation proceeds with a progress report on the product installation as in the following example:

   Execution phase starting . . .: The following product will be installed to destination: DEC AXPVMS GNV V2.1 DISK$ALPHASYS:[VMS$COMMON.] Portion done:0%...10%...20%...30%...40%...50%...60%...70% ...80%...90%..100% The following product has been installed: DEC AXPVMS GNV V2.1 Layered Product

   
   When the installation procedure is complete, the system returns you to the DCL prompt ($).

7. Finally, perform the steps described in Section 11 to set up GNV properly.

You can use the PRODUCT INSTALL command to install GNV on a location other than the system disk by specifying the location with the /DESTINATION qualifier. The target disk must be an ODS-5 disk.

The procedure for installing GNV on a location other than the system disk is equivalent to the steps outlined in Section 9.1, except the PRODUCT INSTALL command format in step 3 would be:

$ PRODUCT INSTALL GNV /SOURCE=device-name:[GNV.KIT] /DESTINATION=device-name

Note that the GNV$STARTUP.COM file is placed in the [SYS$STARTUP] directory on the target disk. You must either copy it to your SYS$COMMON:[SYS$STARTUP] directory or invoke it on the target disk from your SYS$MANAGER:SYSTARTUP_VMS.COM file. For more information on the SYS$STARTUP.COM file, see Section 11.

9.3 If You Move the Target Disk After Installation

The installation procedure creates file GNV_DESTINATION_Alpha.COM or GNV_DESTINATION_IA64.COM in the [SYS$STARTUP] directory. This file points to the target location of the GNV kit, including the physical device specification of the target disk. If you should move the disk on which you installed GNV, edit the SYS$STARTUP:GNV_DESTINATION_archname.COM file so that the device specification correctly reflects the new location.

9.4 Installing the GNV Software in a Cluster

GNV can be installed in a cluster, where the cluster has a common system disk.

GNV must be installed on a common system disk from any one nodes in a cluster. GNV and its directory stucture can be accessed from the other nodes in a cluster by executing the following GNV startup commands:

$ @SYS$SYSDEVICE:[PSX$ROOT]GNV_SETUP.COM $ @SYS$STARTUP:GNV$STARTUP.COM

9.5 Upgrading the GNV Software

The procedure of upgrading GNV is similar to the procedure of installing GNV. To upgrade GNV from Version 2.1-1 or Version 2.1-2 to GNV Version 2.1-3, execute the following command at the DCL prompt:

$ PRODUCT INSTALL GNV

An output similar to the following is displayed:

The following product has been selected: DEC AXPVMS GNV V2.1-3 Layered Product Do you want to continue? [YES] YES The following product will be installed to destination: DEC AXPVMS GNV V2.1-3 DISK$ALPHA83:[VMS$COMMON.] The following product will be removed from destination: DEC AXPVMS GNV V2.1-2 DISK$ALPHA83:[VMS$COMMON.] The following product has been installed: DEC AXPVMS GNV V2.1-3 Layered Product The following product has been removed: DEC AXPVMS GNV V2.1-2 Layered Product

10 Uninstalling the GNV Software

$ PRODUCT REMOVE GNV

An output similar to the following is displayed:

The following product has been selected: DEC AXPVMS GNV V2.1-3 Layered Product Do you want to continue? [YES] Continue the procedure by pressing the Enter key for the default (YES). The following product has been removed: DEC AXPVMS GNV V2.1-3 Layered Product

10.1 Older Version of GNV Files

If the new GNV kit is reinstalled into the same destination directory that was specified during previous installation or if the default location was used, the new kit will replace all the older version files with the newer version files in the same installation directory. If you are reinstalling GNV in the same installation directory, do not execute $ PRODUCT REMOVE GNV .

If the new GNV kit is reinstalled into a new location using
/DESTINATION =<new_installation_location>, the previous version of GNV needs to be removed manually using the following command before reinstallation:

$ PRODUCT REMOVE GNV

GNV provides the following command procedures for use with your system.

1. SYS$STARTUP:GNV$STARTUP.COM --- This file, located in the [SYS$STARTUP] directory of the disk on which you installed GNV, should be executed automatically at startup time. To have it executed at startup time, add the following line to your SYS$MANAGER:SYSTARTUP_VMS.COM file if you installed GNV on the system disk:

   $ @SYS$STARTUP:GNV$STARTUP.COM

   
   If you installed GNV on a disk other than the system disk, add the following line instead, where device-name is the device specification of the disk where GNV was installed.

   $ @device-name:[SYS$STARTUP]GNV$STARTUP.COM

   
   This startup file makes certain required systemwide definitions. Most importantly, it defines the GNU logical to point to the GNV top level directory.

2. GNU:[LIB]GNV_SETUP.COM --- This file is to be executed by each user who will be using GNV. A user can have the file executed automatically at login by incorporating it in the user's LOGIN.COM file. If all users of a system will be using GNV, then this file may be executed in the systemwide LOGIN.COM file: SYS$MANAGER:SYLOGIN.COM.
   This file defines certain process-private symbols that cannot be implemented systemwide. These must be implemented on a per-user basis.
3. SYS$STARTUP:PSX$UP_STARTUP.COM --- This file, located in the [SYS$STARTUP] directory of the disk on which you installed GNV, will be executed automatically at startup time by the GNV$STARTUP.COM procedure. In addition to defining a few logical names to support GNV operation, it also calls the mnt utility to connect all mounted disk volumes under the /mnt directory. If you wish to mount the OpenVMS disks into the Posix view of the file system in a different way, it is recommended that you modify that file by commenting out the call to the DoMountPoints subrouutine, and insert a line which calls your own command procedure with @.

To use GNV, enter the bash command at the OpenVMS DCL prompt. The bash$ prompt will then appear, as in the following example.

$ bash bash$

Enter bash commands at this prompt, as shown in the following example, in which the ls command is entered:

bash$ ls

Alternatively, you can enter a single bash command at the OpenVMS DCL prompt, in the following format:

$ bash -c bash-command

For example, to enter the ls command from the OpenVMS DCL prompt, type the following line. After the contents of the working directory are displayed, the OpenVMS DCL prompt appears again.

$ bash -c ls accountng.dat desktop.dir errorlog. app.exe help.dir $

If the command you are entering has two or more components, the command and components must be surrounded by double quotes as in the following example:

$ bash -c "ls -al"

13 General Environmental Differences Between GNV/OpenVMS and UNIX Systems

This section discusses some of the differences observed between GNV features and utilities on OpenVMS and their counterparts on UNIX systems.

13.1 Root Directory

OpenVMS systems do not have a single root directory similar to that of UNIX systems. The UNIX root directory (/) is the top level of the system file hierarchy. All directories on the system, irrespective of the physical device, are located under the root. On a native OpenVMS system, the closest entity to the UNIX root directory is the toplevel directory of a specific device. The character "/" is not recognized as a directory.

OpenVMS V8.3 has a new feature in the SET ROOT command to specify the location of the root directory. GNV points this root at the primary GNV directory, generally on the system disk. Furthermore, GNV creates a number of directories commonly found immediately under a UNIX root directory: /etc , /usr , /bin , /lib ,. and so forth.

This root directory is the top level of the GNV directory tree. You may use it to locate numerous files and directories. However, unlike a UNIX system, it is not true that all files and directories in the system can be found under the root. To accomplish that, the GNV utility mnt is used to connect all mounted disks to directory entries under the /mnt directory when the

13.2 Multiple Versions of a File

OpenVMS operating systems maintain multiple versions of a file, with the highest version number being the most recent. UNIX maintains only the most recent version of a file. With a few exceptions, GNV supports this UNIX feature. For example, the rm utility removes all versions of a file. The following are some of the utilities that still act only on the most recent version of a file, leaving earlier versions in place:

• mv
• chmod
• chown
• ln

For example, if you use mv to move (or rename) a file, only the highest version number file is moved. The lower versions (older) files are left in place.

13.3 Case Sensitivity in File Names

Normally, OpenVMS systems are not case sensitive. However, on ODS-5 devices you can enable case sensitivity for file names by using the following command at the OpenVMS DCL prompt or in a login command file:

SET PROCESS/CASE=SENSITIVE/PARSE_STYLE=EXTENDED

13.4 Variances in Interpretation of Characters and Unsupported Characters

The following subsections describe differences in the way OpenVMS GNV and the UNIX operating system interpret certain characters and lists characters that are unsupported.

13.4.1 File Names Beginning with a Period

OpenVMS lets you create a file name beginning with a period. The OpenVMS DIRECTORY command will list such files. UNIX systems consider such files as hidden. The UNIX ls command does not list such files unless, for example, the -a option is used or the file name is specified in the command line.

13.4.2 Control Characters

The following control sequences do not work as expected:

• CTRL/C (the response depends on the circumstances; if you do not get the expected response, try using CTRL/Y to bring you to the DCL prompt, and then enter the DCL CONTINUE command to bring you back to the original prompt or interrupted process)
• CTRL/Y (instead of bringing you to the previous command entered, this sequence might bring you back to the DCL prompt, stopping the bash program; try entering CTRL/Y a second time)

The CTRL/@ sequence has not been tested.

14 GNV Version 3.0-1 Packages Upgrade and Version Difference

In GNV Version 3.0-1, 16 packages are upgraded to the latest GNU level out of 24 total packages. The remaining eight packages are not upgraded from GNV Version 2.1-3. Table 2 lists the GNV Version 3.0-1 packages upgrade and version difference. For more information about the latest GNU packages, see the GNU website at http://www.gnu.org/software .

Table 2 GNV Version 3.0-1 Packages Upgrade and Version Difference

Package Name	GNV V2.1-3	GNV V3.0-1	Upgrade to latest GNU Version	GNU Website
bash	1.14.8	1.14.8	No	http://www.gnu.org/software/bash/
make	3.78.1	3.78.1	No	http://www.gnu.org/software/make/
gawk	3.1.1	3.1.8	Yes	http://www.gnu.org/software/gawk/
bzip2	1.0.2	1.0.6	Yes	http://www.bzip.org/
Coreutils	2.0, 2.1, and 4.1	8.5	Yes	http://www.gnu.org/software/coreutils/
Diffutils	2.7	3.0	Yes	http://www.gnu.org/software/diffutils/
file	4.09	5.04	Yes	http://www.darwinsys.com/file/
findutils	4.1	4.4.2	Yes	http://www.gnu.org/software/findutils/
grep	2.4.2	2.7	Yes	http://www.gnu.org/software/grep
gzip	1.2.4	1.4	Yes	http://www.gzip.org/
unzip	5.42	6.0	Yes	http://www.info-zip.org/
zip	2.3	3.0	Yes	http://www.info-zip.org/
less	358	418	Yes	http://www.gnu.org/software/less/
man	1.5k	1.5k	No	http://primates.ximian.com/~flucifredi/man/
mnt	2.8	2.8	No	OpenVMS Specific development
patch	2.5.4	2.6	Yes	http://savannah.gnu.org/projects/patch
sed	3.02	4.2.1	Yes	http://directory.fsf.org/project/sed/
gnutar	1.19	1.25	Yes	http://www.gnu.org/software/tar/
vitpu	1.4	1.4	No	OpenVMS Specific development
vim	6.3	7.3	Yes	www.vim.org
vmstar	3.4	3.4	No	http://vms.process.com/scripts/ fileserv/fileserv.com?VMSTAR
which	2.16	2.2	Yes	http://savannah.gnu.org/projects/which
vmsutils	No	No	No	OpenVMS Specific development
wrapper	No	No	No	OpenVMS Specific development