Versions Compared

Old Version 18

changes.mady.by.user Mark Henry

Saved on

compared with

New Version 19

changes.mady.by.user Mark Henry

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Become the superuser with sudo, su, etc.

  2. Pick a suitable directory
    root's home directory is likely ok. Running mount should confirm - look for noexec. We recommend that you use an empty new temporary directory for the installer as that simplifies cleanup.

    Code Block
    cd; # you're in root's homedir now. or pick some other writable and executable place
mkdir installertemp

  3. Tell the installer to use this local temporary directory and start the installation

    Code Block
    export TMPDIR=installertemp
# this assumes that opProduct was downloaded/transferred into root's homedirectory; adjust the path accordingly if not. 
sh ./opProduct-version.run

  4. Clean up the temporary directory

    Code Block
    rm -rf installertemp
unset TMPDIR

NOTE: It is important to understand that the omkd daemon, which is required for rendering the GUI via Apache also requires the /tmp directory to be mounted as executable or the daemon will crash after start. You can. however, redefine the /tmp directory for omkd by adding the following lines into /etc/init.d/omkd

Code Block
title/etc/init.d/omkd
TMPDIR="/newtmp"
export TMPDIR

Add them at line 18 (after the line # Do NOT "set -e").

Obviously, /tmpdir will need to exist. If the admin of the box needs to run any OMK programs manually, they will need to have exported /tmpdir before they do so.

Available Installer Options

...