NOTE: This release of SCO Skunkware is a pre-release special edition. As such, several of the components have not been thoroughly tested. Please report any problems you encounter by e-mailing skunkware@ronrecord.com so that we can correct any errors prior to subsequent inclusion in future releases of SCO OpenServer or UnixWare 7.
Table of Contents
The very latest Release Notes for Skunkware can be found at http://skunkware.dev/skunkware/relnotes.html.
To obtain additional SCO Skunkware pre-built for use on SCO OpenServer or UnixWare 7, see the SCO Skunkware Web Site or you may wish to order the Skunkware CD.
Distributions are released on CD periodically and a repository of this and previous distributions as well as updates and corrections can always be found at http://skunkware.dev/skunkware.
SCO Skunkware contains a wide variety of software ranging from educational and experimental research tools to commercial grade software suitable for use on a production server.
It is provided for free and is not formally supported by SCO.
To determine the licensing conditions for a particular component, see the corresponding source in the source directory. With the infrequent exception of SCO proprietary code, all Skunkware components are accompanied by the source used to build them. The source is archived in the src subdirectory by category. The categories are:
Skunkware Software Categories | ||||||||
---|---|---|---|---|---|---|---|---|
audio | emulators | libraries | shellutil | fileutil | sysadmin | db | net | |
textproc | devtools | interp | news | video | editors | lib | shells | www |
X11 Graphical Categories | ||||||||
apps | fonts | games | graphics | misc | savers | utils | viewers | winman |
Remember, Skunkware is freely distributed and unsupported software. No warranty is made on any of the Skunkware components. Support and assistance with this software is not provided by SCO. In many cases, however, an e-mail to skunkware@ronrecord.com describing any problem you might have may result in a reply/fix/solution. And ...
The Santa Cruz Operation, Inc. and SCO Skunkware are not related to, affiliated with or licensed by the famous Lockheed Martin Skunk Works (R), the creator of the F-117 Stealth Fighter, SR-71, U-2, Venturestar(tm), Darkstar(tm), and other pioneering air and spacecraft.
[Note that it is not necessary to mount the Skunkware CD-ROM in order to install the pkgadd or custom installable packages. See the section below on installing the Skunkware software.]
To mount the Skunkware CD-ROM on an SCO UnixWare system, use the command:
# mount -r -f cdfs /dev/cdrom/cdrom1 /mount-pointwhere mount-point refers to the full pathname of the directory on which you wish to mount the CD-ROM (e.g. /mnt). Note also that the CD-ROM device name may vary from system to system.
On an SCO OpenServer Release 5 system issue the command:
# mount -r /dev/cd0 /mount-point
The installation of all the Skunkware components can require several hundred Megabytes of free space on the root partition (/usr/local). If your root partition does not have sufficient space, or you wish to utilize an alternate filesystem for the Skunkware components, prior to installing Skunkware create a symbolic link in /usr as follows (using /u as the alternate filesystem):
On UnixWare # mv /usr/local /u/local # ln -s /u/local /usr/local On OpenServer # mkdir /u/SKUNK99 # ln -s /u/SKUNK99 /opt/K/SKUNK99The above commands assume a separate /u filesystem with sufficient disk space. The exact name of the alternate filesystem mount point is system dependent.
# /mnt/INSTALLThe Skunkware INSTALL script will allow you to select from a menu of Skunkware "software sets" including All Components, Development Tools, Shells, Audio/Video Components, etc. The INSTALL script acts as a front-end for a non-interactive installation using the Software Manager (pkgadd or custom).
NOTE: A full installation of SCO Skunkware will consume several hundred Megabytes of disk space and take a couple of hours.
To install an individual package on UnixWare, execute the command:
# pkgadd -d /mnt PackageIf the Skunkware CDROM is not mounted, execute the command:
# pkgadd -d /dev/cdrom/cdrom1 PackageTo install an individual package on OpenServer, execute the command:
# /etc/custom -p SKUNK99:default:Package -i -m /dev/rcd0where "Package" is the name of the desired component and /mnt is the mount point of the Skunkware CDROM. See the file /mount-point/COMPONENTS for the list of available components.
After completing the installation of the Skunkware components you desire, you may wish to add /usr/local/bin to your PATH and /usr/local/man to your MANPATH. You may also wish to add /usr/local/java to your CLASSPATH. It should not be necessary to add /usr/local/lib to your LD_LIBRARY_PATH as the Skunkware shared libraries have been built with the appropriate flags.
For an introductory tour, point a web browser at /mount-point/index.html
# /usr/bin/X11/netscape file:/mount-point/index.htmlIf you do not have Netscape Navigator installed, download a trial copy from http://www2.sco.com or use any browser that supports tables and open the URL file:/mount-point/index.html (assuming you mounted the CD on /mount-point).
If you do not have or want a graphical browser, you can use Lynx (a character browser) which is included as part of the UnixWare 7 installation and as a Skunkware 99 component. Execute the command:
# lynx file:/mount-point/index.html
SCO Skunkware 99 contains files suitable for installation with the SCO Software Manager (pkgadd or custom). In addition, there are hundreds of source archives
All of the Skunkware 99 software can be removed by issuing the command:
# /mount-point/REMOVEwhere mount-point indicates the directory on which the Skunkware CDROM is mounted. Individual components can be removed with the command:
UnixWare # pkgrm Component OpenServer # /etc/custom -p SKUNK99:default:Component -rwhere Component is the individual component name.
A list of all installed Skunkware components can be retrieved with:
UnixWare # pkginfo -c skunkware OpenServer # /etc/custom -p SKUNK99:default -l
Accessing the CD on other platforms
On any other system, after mounting or otherwise making the High-Sierra Rockridge CD-ROM filesystem accessible, point your WWW browser to mount-point/index.html where mount-point indicates the UNIX directory or Windows drive representing the CD-ROM.
In almost all cases, source code is available, so you can rebuild for earlier SCO releases or other platforms. A full source archive for this and previous Skunkware releases is available at either http://skunkware.dev/skunkware/src/ or ftp://ftp.sco.com/skunkware/src/.
Source code is provided in the
src directory.
In some cases, source code is provided but no
compiled binaries. The source distributions are in bzip2 compressed
tar or cpio format. In order to extract these, use the command:
$ bunzip2 -c /mount-point/src/<directory>/<package>.tar.bz2 | tar xf -
or, in the case of a compressed cpio archive:
$ bunzip2 -c /mount-point/src/<directory>/<package>.cpio.bz2 | cpio -icdu
Where <directory> refers to the top-level source directory
and <package> is the package name (e.g. gzip-1.2.4).
If you do not have bunzip2 installed (part of the bzip2 package), you can install it off of the SCO Skunkware 7.1 or 98 CD via the command:
UnixWare # pkgadd -d /mount-point bzip2 OpenServer # /etc/custom -p SKUNK98:default:Bzip2 -i -m /dev/rcd0Precompiled binaries for use on SCO OpenServer and UnixWare systems can be found in /mount-point/osr5/bin, /mount-point/uw7/bin and /mount-point/uw2/bin.
You may also find the SCO Technical Library Supplements to be of interest. These are drawn from the SCO Support Online System, and are accessible via anonymous ftp on the Internet from ftp.sco.com or via web facilities at http://www.sco.com
Default Package Configurations
Many of the Skunkware packages contain configuration files. In order to avoid excessive user interaction during installation and to provide a consistent and well integrated set of configurations, the Skunkware packages have been pre-configured with commonly used default values.
Generally, you will not need to alter the default configurations but you may choose to do so. Some of the package pre-configurations are as follows:
$ /usr/local/bin/wmaker.instOn OpenServer, enter ".startxrc" when prompted for the name of the X11 session startup script. On UnixWare 7, enter either ".xsession" or ".xinitrc". Modify the resultant file in your home directory to select the type of graphical login session you desire. If your selected session type fails, edit this file and select either fvwm95 or pmwm to verify that your setup is correct.
Known Limitations and Problems
On UnixWare # mv /usr/local /u/local # ln -s /u/local /usr/local On OpenServer # mkdir /u/SKUNK99 # ln -s /u/SKUNK99 /opt/K/SKUNK99Where /u denotes an additional disk or filesystem with sufficient space.
Source for KDE can be retrieved either from the KDE ftp site at ftp.kde.org or from the Skunkware ftp site at ftp://ftp.sco.com/skunkware/src/x11/winman/kde/
If you wish to setup the root user with a KDE environment, after starting KDE as root you will need to edit the file /.kde/share/apps/kfm/desktop and change all occurrences of "file://..." to "file:/...". Exit the root KDE session and restart another. Root's desktop icons should now function properly.
Note that KDE is not small. Running on a system with less than 64 Megabytes of RAM can, at times, be slow. Running on a system with less than 32 Megabytes has not been tested and is not recommended.
It is hoped that this remarkable new desktop environment will please the graphical Skunkware user.
# ps -ef | grep X # kill <pid>
$ xset -fp /usr/local/share/fonts/freefont $ xset +fp /usr/local/share/fonts/freefont $ xset fp rehashThe gimp command has been wrappered with a shell script which does this for you.
We are interested in your general comments about this distribution and about development tools in general. Please feel free to e-mail skunkware@ronrecord.com with comments, criticisms and suggestions.
Ron Record | rr@ronrecord.com |
Open Source Program Architect | SCO |
400 Encinal St. | Santa Cruz, CA 95061 |