Qedit Trial Release
Installation Instructions
You may want to print this page, for reference.
FTP upload of binary file to HP-UX
Once you have downloaded the binary file to your PC, you need to upload it to the HP 9000.
Please note that the file you downloaded ended in a .Z, however, some browsers especially IE will try and help you and rename file file to be .tgz. Simply rename the file back to .Z when you upload the file or after you upload to your server.
Using your favorite FTP utility, connect as root, and use a binary transfer to PUT the file to the HP-UX server.Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Downloads>ftp dev.robelle.com Connected to dev.robelle.com. 220 HP ARPA FTP Server User (dev.robelle.com:(none)): root 31 Password required for root. Password: 230 User root logged on ftp> binary 200 Type set to I. ftp> cd /tmp ftp> put qxprod.Z ftp> quit 221 Server is closing command connection
The .Z problem
Some ftp clients do not preserve the case in the filename and end up upshifting or downshifting the filename depending on the settings of your ftp client. Some customers have ftp'ed the qxprod.Z file only to end up with the filename as qxprod.z.
This impacts our installation, as compress does not find the file to decompress; or worse, if a file of the same name exists that does have the capital Z at the end, then that (typically older) file is used and you end up installing an older version.
To insure that the following steps work properly please double check that the file you just ftp'ed is placed on the server with the proper name and has a .Z (dot Capital Z) and not the small ".z". You can always rename the file with the .z over top of the file with the .Z with the following:
mv qxprod.z qxprod.Z
Installing the Software
Once you have the file on your HP 9000, you need to install it:
- Restore the files.
- Apply the license codes.
Restore the files
Logon as root.
su - cd /tmp
Decompress the download:
compress -d qxprod
Create the directory where the Qedit files will reside:
mkdir /opt/robelle
Unpack the Robelle files:
cd /opt/robelle tar xvf /tmp/qxprod
Apply the license codes
Using the codes provided in your e-mail from Robelle, execute the following installations steps.
cd /opt/robelle/bin ./extend Product Verification code: n Verification code: n
You can now run Qedit:
/opt/robelle/bin/qedit
Cleanup
If Qedit runs and you like to keep things clean like we do, we recommend that you remove the tar file with:rm /tmp/qxprod
Checking Permissions
When signing on as root on a security hardened system and creating the robelle directory it may be that only the root user who can run whatever software you are installing.You can tell a system that has been hardened typically with a umask command, which will return:
077What ends up happening when you make a directory with mkdir is the permissions end up being 700 or rwx for root, --- for group, and --- for user. The solution to this is to change the permissions:
chmod -R 755 /opt/robelle
Setting up Environment Variables
If this is an upgrade then it is likely that all the environment variables have been setup and you can skip this section.You can set up various environment variables to make running any of the Robelle products easier. The four variables that we recommend setting for Qedit are: SHLIB_PATH, ROBELLE, PATH and MANPATH.
- The ROBELLE variable tells the Robelle products where it's supporting files are located.
- The PATH variable, when set, allows the user to run Qedit by just typing "qedit" instead of the fully qualified program name.
- The MANPATH variable, when set, allows users to access the manpage (Help page) for Qedit.
ROBELLE, PATH and MANPATH
The easiest way to add variables accessible to all users is to set the variables in the global exec file for the shell you use.
For the Bourne, Korn and Posix Shells we recommend the following additions to the /etc/profile file.
export ROBELLE=/opt/robelle export PATH=$PATH:$ROBELLE/bin export MANPATH=$MANPATH:$ROBELLE/man
For the C Shell we recommend that you add the following commands after any existing PATH or MANPATH statements in the /etc/csh.login file:
setenv ROBELLE /opt/robelle set path=($path $ROBELLE/bin) setenv MANPATH "$MANPATH":$ROBELLE/man
Configuring different Shells
When you log on to HP-UX, a program is run called the shell. The shell program interprets commands, executes them, and controls command execution. Making configuration changes requires that you know which shell you are using and what files are automatically executed.
Bourne, Korn and Posix Shells
The Bourne, Korn and Posix shells execute the file /etc/profile when you log on to HP-UX. They then look for a file in your home directory called .profile. If it exists, it is executed. If you use SAM to add new users, the file /etc/d.profile is automatically copied to the home group of the new user. If you want to make global changes to the commands that are executed at login in time you typically have to make the changes to the /etc/profile file, and check that the /etc/d.profile (the file that becomes the users .profile file), does not counteract any of the changes that you have made to the global file, such as Path, Manpath or Robelle. You also have may have to warn existing Bourne and Korn shell users to change their .profile file in their home directories.