ch52_05.htm

the unix power tools

></LI
><LI
CLASS="listitem"
><P
CLASS="para"
>SCO UNIX 3.2.4</P
></LI
></UL
><P
CLASS="para"
>The pre-compiled binaries may work on operating system
versions slightly older or newer 
than the ones listed here.
Some programs take advantage of features that
are not supported on all the platforms.
The install program will tell
you if a program is not available for your platform.</P
><P
CLASS="para"
>If you are uncertain of your operating system
version, the <EM
CLASS="emphasis"
>uname</EM
> command may help:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>uname -a</B
></CODE
>
SunOS ruby 4.1.4 1 sun4m</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>If your platform is not listed, you should try building the
programs from source code as described in article
<A
CLASS="xref"
HREF="ch52_08.htm"
TITLE="Building Programs from Source Code "
>52.8</A
>.</P
><DIV
CLASS="sect3"
><H4
CLASS="sect3"
><A
CLASS="title"
NAME="UPT-ART-9503-SECT-1.3.1"
>52.5.3.1 Directory Structure </A
></H4
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62805"
></A
><A
CLASS="indexterm"
NAME="AUTOID-62807"
></A
>There is a standard installation structure for 
all packages on the CD-ROM.
Using this structure (and some simple variations of it), you can tailor 
how and where your packages will be installed on your system.</P
><P
CLASS="para"
>The basic directory structure is shown in 
<A
CLASS="xref"
HREF="ch52_05.htm#UPT-ART-9503-FIG-0"
TITLE="Basic Directory Structure"
>Figure 52.1</A
>.</P
><H4
CLASS="figure"
><A
CLASS="title"
NAME="UPT-ART-9503-FIG-0"
>Figure 52.1: Basic Directory Structure</A
></H4
><IMG
CLASS="graphic"
SRC="figs/9503a.gif"
ALT="Figure 52.1"><P
CLASS="para"
>Some packages may deviate from this structure by having extra directories 
at the <EM
CLASS="emphasis"
>&lt;install_dir&gt;</EM
> level.</P
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62818"
></A
><A
CLASS="indexterm"
NAME="AUTOID-62820"
></A
><EM
CLASS="emphasis"
>Shareable</EM
> files are those files that are machine independent and
can be shared across many machines in a network using a
<SPAN
CLASS="link"
>network filesystem (NFS) (<A
CLASS="linkend"
HREF="ch01_33.htm"
TITLE="UNIX Networking and Communications "
>1.33</A
>)</SPAN
>.
These are typically text files, such as manual pages or &quot;include files.&quot;
Sharing files reduces the amount of disk space required by allowing several 
different
systems to use the same set of files, as opposed to having to duplicate them for
each machine.
It also simplifies administration of the files by having only
a single copy to maintain.</P
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62825"
></A
><EM
CLASS="emphasis"
>Non-shareable</EM
>
files are machine/architecture specific and may not be shared (except
with other hosts of the same architecture).
These are typically binaries
or data files that depend on a certain architecture or byte order.</P
><P
CLASS="para"
>The installation program gives you the ability to split the shareable
and non-shareable files into separate directories.
Using this scheme, you could
put shareable files onto a partition or directory that is mounted by multiple
machines.</P
><P
CLASS="para"
>If you want to store shareable and non-shareable files at the same directory
level, the shareable directories will be preceded by a leading <EM
CLASS="emphasis"
>s</EM
> to mark
them as &quot;shareable.&quot;
For example, <EM
CLASS="emphasis"
>sbin</EM
> is shareable, 
while <EM
CLASS="emphasis"
>bin</EM
> is non-shareable.</P
><P
CLASS="para"
>[1]
<A
CLASS="xref"
HREF="ch52_05.htm#UPT-ART-9503-FIG-1"
TITLE="Default Installation Directory Structure"
>Figure 52.2</A
>
shows how the default installation directories are arranged.</P
><BLOCKQUOTE
CLASS="footnote"
><P
CLASS="para"
>[1] You may also remove the leading <EM
CLASS="emphasis"
>s</EM
> from the shareable directories 
<EM
CLASS="emphasis"
>sinclude</EM
>, <EM
CLASS="emphasis"
>sspool</EM
>, <EM
CLASS="emphasis"
>sbin</EM
>, and <EM
CLASS="emphasis"
>slib</EM
>.
This way, you
can merge <EM
CLASS="emphasis"
>slib</EM
> into <EM
CLASS="emphasis"
>lib</EM
>, and <EM
CLASS="emphasis"
>sbin</EM
> into <EM
CLASS="emphasis"
>bin</EM
> if 
your shareable and non-shareable files are stored in the same directory, or
make names clearer if your shareable and non-shareable files
are not stored together.</P
></BLOCKQUOTE
><H4
CLASS="figure"
><A
CLASS="title"
NAME="UPT-ART-9503-FIG-1"
>Figure 52.2: Default Installation Directory Structure</A
></H4
><IMG
CLASS="graphic"
SRC="figs/9503b.gif"
ALT="Figure 52.2"><P
CLASS="para"
>You can modify this structure using the Smart Installation System
and any necessary directories will be created
(if you have permission to do so).</P
><P
CLASS="para"
>In order to run the software after installation, you will need to make sure 
that your shell path variable 
includes <EM
CLASS="emphasis"
>&lt;install_dir&gt;/bin</EM
> (and possibly <EM
CLASS="emphasis"
>&lt;install_dir&gt;/share/bin</EM
>
if you choose to use this structure).
For example, if <EM
CLASS="emphasis"
>&lt;install_dir&gt;</EM
>
is set to <EM
CLASS="emphasis"
>/usr/local</EM
>, set your
<SPAN
CLASS="link"
>search path (<A
CLASS="linkend"
HREF="ch08_07.htm"
TITLE="Setting Your Search Path "
>8.7</A
>)</SPAN
>
as appropriate for your shell:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>set path=($path /usr/local/bin /usr/local/share/bin)</B
></CODE
>   <I
CLASS="lineannotation"
>csh</I
>
$ <CODE
CLASS="userinput"
><B
>PATH=$PATH:/usr/local/bin:/usr/local/share/bin ; export PATH</B
></CODE
>   <I
CLASS="lineannotation"
>sh</I
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>&#13;The installation software will automatically print out a suggested path
when it finishes installing a program.</P
></DIV
><DIV
CLASS="sect3"
><H4
CLASS="sect3"
><A
CLASS="title"
NAME="UPT-ART-9503-SECT-1.3.2"
>52.5.3.2 Starting the Installation </A
></H4
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62866"
></A
>To begin the installation process, become the superuser and mount the CD-ROM.
For example, on a Sun running SunOS 4.1.4:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>su</B
></CODE
>
Password:
# <CODE
CLASS="userinput"
><B
>/etc/mount -r -t hsfs /dev/sr0 /cdrom</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>Then change directories to the mount point you specified for the 
CD-ROM and see what is there.
In our case, we specified
<EM
CLASS="emphasis"
>/cdrom</EM
> as our mount point:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
># <CODE
CLASS="userinput"
><B
>cd /cdrom</B
></CODE
>
# ls
common          install.pt      alpha           linux
hp700           instinfo        rs6000          sun4c
i386            readme          sources         ssol2</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>The output could look slightly different depending on the type of system:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>ALPHA/      CONFIG1      HP700/       INSTINFO/   RS6000/    SUN4C/
BUILD.PT*   CONFIG2.REV  I386/        LINUX/      SOURCES/
COMMON/     CONFIG3.Z    INSTALL.PT*  README      SSOL2/</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>One of the first things that the installation program will do when installing
software is to copy the programs into a &quot;staging&quot; area.
By default, this is
the directory <EM
CLASS="emphasis"
>/tmp</EM
>.
By setting the environment variable <EM
CLASS="emphasis"
>TMPDIR</EM
> to
another directory, you can alter this location.</P
><P
CLASS="para"
>For example, if you want to use the directory <EM
CLASS="emphasis"
>/mondo</EM
> for the staging
area:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>setenv TMPDIR /mondo</B
></CODE
>   <I
CLASS="lineannotation"
>csh</I
>
$ <CODE
CLASS="userinput"
><B
>TMPDIR=/mondo; export TMPDIR</B
></CODE
>   <I
CLASS="lineannotation"
>sh</I
></PRE
></BLOCKQUOTE
></P
><BLOCKQUOTE
CLASS="note"
><P
CLASS="para"
><STRONG
>NOTE:</STRONG
> If you wish to install software in &quot;system&quot; areas, you will likely run into
problems with file permissions.
You can just become the superuser and not
worry about permissions, but this is dangerous because you could overwrite
previously installed or vendor-supplied software.
The other option is to
run the install as an unprivileged user.
This should prevent you from
damaging system areas, but you will have to use
<SPAN
CLASS="link"
><EM
CLASS="emphasis"
>chmod</EM
> (<A
CLASS="linkend"
HREF="ch22_07.htm"
TITLE="Using chmod to Change File Permission "
>22.7</A
>)</SPAN
>
to make directories writable
before you begin the installation process&nbsp;- or possibly
use
<SPAN
CLASS="link"
>group permissions (<A
CLASS="linkend"
HREF="ch22_13.htm"
TITLE="Groups and Group Ownership "
>22.13</A
>)</SPAN
>
to control access.</P
></BLOCKQUOTE
></DIV
><DIV
CLASS="sect3"
><H4
CLASS="sect3"
><A
CLASS="title"
NAME="UPT-ART-9503-SECT-1.3.3"
>52.5.3.3 Running Install </A
></H4
><P
CLASS="para"
>Once you have the CD-ROM properly mounted, 
run the appropriate install command for your system.
For example:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>./install.pt</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>or:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>% <CODE
CLASS="userinput"
><B
>./INSTALL.PT\;1</B
></CODE
></PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>The installation program will display menus and prompt you for input from
now on.
It will also try to guess the type of machine you are running it
on and the mount point of the CD-ROM:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>Assuming CDROM   is mounted at /archive/cdrom
Assuming MACHINE is ALPHA

                      Welcome to Ready-to-Run Software's
                         * Smart Installation System *

This installation system requires write permission in /tmp (or $TMPDIR if
it's set) directory (for staging the install) and write permission in the
installation directory for the actual install (these may be the same).
     ...</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62911"
></A
>At this point, the installation program may ask if you want to use a
different
<SPAN
CLASS="link"
><EM
CLASS="emphasis"
>umask</EM
> (<A
CLASS="linkend"
HREF="ch22_04.htm"
TITLE="Setting an Exact umask "
>22.4</A
>)</SPAN
>
value for the installation process:  </P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>Use umask of 022 instead of 007 for install [y]? y</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>This will affect the permissions of the software when it is
installed. The suggested value of 022 will allow anyone to execute or
read the programs, but gives write permission only to you.</P
><P
CLASS="para"
>The install program will then present a list of the available
software:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>The PowerTools2 package contains the following scripts:

!            80cols       Clear        _emacs_ml    _enter_csh   _enter_sh    
_exit_csh    _exit_sh     addup        age_files    ascii        awf          
behead       bkedit       cal_today    catsaway     center       cgrep        
   ...


The PowerTools2 package contains the following packages:

bash         bitmaps      bsdtar       bsplit       calen        cpmod
cvtbase      delete       diff         ediff        emacs        fgrep
fileutils    find         gawk         getopt       glimpse      grabchars
   ...</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>After the names of the software packages have been displayed, you are
prompted for which ones to install:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>Enter the name of a package to install or choose Search, Quit or All
&lt;package&gt;, S(earch), A(ll), Q(uit) [Search]?</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>You can now type the name of the package, search for packages, quit the
installation program, or install all packages in one fell swoop.</P
></DIV
><DIV
CLASS="sect3"
><H4
CLASS="sect3"
><A
CLASS="title"
NAME="UPT-ART-9503-SECT-1.3.4"
>52.5.3.4 Installing a Single Program </A
></H4
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="UPT-ART-9503-IX-INSTALLATION-PROCESS-FOR-SINGLE-PROGRAM-SINGLE"
></A
>Some of you might prefer not to install the entire distribution, 
but just selected programs.  </P
><P
CLASS="para"
><A
CLASS="indexterm"
NAME="AUTOID-62932"
></A
>For this example, let's assume you are looking for programs that do something
with terminals, but you don't know what they are called.
You can use the
&quot;Search&quot; function at the main menu to look for you.
Just press RETURN at the prompt, as the &quot;Search&quot; is the
default action in the square brackets (<CODE
CLASS="literal"
>[]</CODE
>).</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>&lt;package&gt;, S(earch), A(ll), Q(uit) [Search]? s</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>Then type in &quot;terminal&quot; for the search keyword:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>Search package descriptions for (? for help) []? terminal</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>All packages matching this description will be displayed:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>The descriptions for the following packages mention &quot;terminal&quot;:
   1.  Clear
   2.  emacs
   3.  qterm
   4.  screen
   5.  tcap
   6.  termtest
   7.  tputinit

   A.  ALL
   N.  NONE

Choose one please:</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>For this example, the <EM
CLASS="emphasis"
>qterm</EM
> program is selected, which is option 1:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>Choose one please: 3</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>A description of the program is now displayed:</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>qterm - version 5.0         Version 5.0

Qterm is a program that queries terminals to find out what kind of
terminal is responding.  It is useful to automagically define your
terminal type.  It prints the name of the terminal (compatible,
hopefully, with a termcap/terminfo name) such as &quot;vt100&quot; to standard
output.

The qterm package is approximately  64Kb
     32Kb - Required
     15Kb - Shared: Formatted Man pages
      3Kb - Shared: Other Shareable files
     13Kb - Shared: Unformatted Man pages

Install qterm [y]?
qterm was compiled and made &quot;Ready-to-Run&quot; by
        Ready-to-Run Software, Inc.


   Copyright (c) 1990 Michael A. Cooper.
   This software may be freely distributed provided it is not sold for
   profit and the author is credited appropriately.

Power Tools distribution by permission of the author.

                               ************************</PRE
></BLOCKQUOTE
></P
><P
CLASS="para"
>After information about <EM
CLASS="emphasis"
>qterm</EM
> is printed, you are told how much
space it will require and then asked whether you want it installed.
Press RETURN to install it, or &quot;n&quot; for &quot;no&quot; (followed by
RETURN) if you don't want it installed. For our example, we
want <EM
CLASS="emphasis"
>qterm</EM
> installed, so we just press RETURN.</P
><P
CLASS="para"
><BLOCKQUOTE
CLASS="screen"
><PRE
CLASS="screen"
>The qterm package is approximately  56Kb
     24Kb - Required
     15Kb - Shared: Formatted Man pages
      3Kb - Shared: Other Shareable files
     13Kb - Shared: Unformatted Man pages

Install qterm [y]? <KBD
CLASS="keycap"
>[RETURN]</KBD
></PRE