About Robelle

Qedit Pre-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.

(Example using Reflection FTP Client)

(Example using MS-DOS FTP Client)

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 small z over top with a:

mv sxprod.z sxprod.Z

Preparing for Install

In order to install Qedit for HP-UX you must be sure that no one else is accessing and that the Qedit server is not running. You can check this normally with a:

	ps -ef | grep qedit
If any copies of Qedit are running you will need to insure that the users save their files and if you have the Qedit server daemon running you will need to kill that process once the users have logged off and saved their files.

If the server is running you would likely see:

	ps -ef|grep qedit
    root 14368     1  0 13:30:13 ?         0:00 ./qedit -d
You would need to kill the process associated with the server. If you don't see the qedit -d you are not running the server option. Please note that you would need to restart the server once the new version has been installed. You can find information on starting the server in the Qedit for Windows Change Notice

Installing the Software

Once you have the file on your HP 9000, you need to install it:

  1. Restore the files.
  2. Apply the license codes.

Restore the files

Logon as root.

su -

Decompress the download:

compress -d qxpre

Create the directory where the Qedit files will reside:

mkdir /opt/robelle

Unpack the Robelle files:

cd /opt/robelle
tar xvf /home/root/qxpre

Wait to be contacted by Robelle with the authorization codes.

Apply the license codes

Once you get the codes you can apply them:

cd /opt/robelle/bin
Product Verification code: n
Verification code: n
Verification code: n

You can now run the pre-release:


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:

What 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 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

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)

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.

C Shell

The C shell executes the file /etc/csh.login when you log on to HP-UX. It then looks for the file .login in your home directory. If it exists, it is executed. Next, the C shell executes the file .cshrc in your home directory (also executed any time you invoke a new copy of /bin/csh). If you use SAM to add new users, the files /etc/d.login and /etc/d.cshrc are automatically copied to the home group of the new users. You may need to make changes to /etc/d.login and /etc/d.schrc, so that new users do not override your changes. You may also have to warn existing C shell users to change their .login and .cshrc files in their home directories.


See the change notice for full documentation on the new release, including the setting of environment variables.