Welcome!

. . . . . . . SCO Skunkware FAQ

Created and maintained by Ronald Joe Record (rr@sco.com)

What is SCO Skunkware?

SCO Skunkware is the generic name for a free collection of software prebuilt for SCO systems. This distribution is Skunkware 7 (the distribution naming is rather eclectic) and is targeted mainly at the Unixware 7 platform though there are packages here for both UW 2.x and OpenServer. Previous releases of SCO Skunkware provided tools ported to SCO OpenServer, SCO UnixWare 2.x, SCO ODT, SCO UNIX 3.2v4, and even SCO Xenix.

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://www.sco.com/skunkware.

SCO Skunkware is software for entertainment, education, experimentation, and often real work. It is provided for free and is not formally supported by SCO.

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.

[top]

How do I order the SCO Skunkware CD-ROM?

The currently shipping SCO Skunkware CD-ROM may be ordered from our on-line ordering system which has been updated to include SCO Skunkware. There is no additional media, shipping or handling charge for SCO Skunkware when ordered in conjunction with any of the other SCO "free" product offerings.

Previous releases of SCO Skunkware are no longer available on CD-ROM, but may be downloaded from our previous release web/ftp site.

[top]

How do I locate a particular SCO Skunkware component?

To download a particular component you first have to locate the download directory for that component. The SCO Skunkware team has tried to provide intuitive categories of components. For instance, if you were looking for Vim, the improved visual text editor, you could click on Editors from the Category Selection page.

Similarly, the SCO Skunkware ftp hierarchy has been organized by functional category within operating system platform. For instance, to find the SCO OpenServer "vim" distribution via ftp, you would establish an anonymous ftp connection to ftp.sco.com and look in the directory /skunkware/osr5/editors. There you would find a subdirectory called vim. To locate the SCO UnixWare vim distribution, you would look in the directory /skunkware/uw7/editors.

You can also locate a Skunkware component by searching the HTML documents on www.sco.com.

[top]

How do I download "xyz" for SCO OpenServer?

Make sure to download files in binary mode when using ftp. To download with your web browser, simply hold the shift key down while clicking on the desired file. The OpenServer Skunkware distribution is available via http and ftp at either :

After locating a component's download directory (see the previous answer), the typical OpenServer Skunkware distribution will contain several files. These include :

Media images installable with the SCO Software Manager (custom)
This is the file "VOLS.tar", a tar archive of custom installable media images. This is the preferred and recommended downloadable and installable component format.
A gzip'd tar or cpio archive
This file is typically named component-release.tar.gz or component-release.cpio.gz where "component-release" stands for the name and release of the component (e.g. vim-4.6). This is an alternate distribution format which is intended for those people who dislike using the SCO Software Manager (custom) or for components which have not yet been packaged for use with custom.

This file contains a binary distribution which can be extracted by hand as the root user from / on the target system. If a VOLS.tar file exists for this component, it is recommended to download that and install using custom.

Source for the component
There should always be a gzip'd tar archive of the source used to build a particular Skunkware component as well as a pointer back to the original source (often they are identical). This source archive is usually stored in the "src" subdirectory of the download directory for a component. For instance, the source to vim is in the directory /skunkware/osr5/editors/vim/src. This directory (and the one at /skunkware/uw7/editors/vim/src) is a symbolic link to the single source directory that contains the source archives for all platforms. For instance, the vim source is actually located at /skunkware/src/editors/vim) and is linked into the osr5 and uw7 trees.

[top]

How do I download "xyz" for SCO UnixWare?

Make sure to download files in binary mode when using ftp. To download with your web browser, simply hold the shift key down while clicking on the desired file. The UnixWare 2.x Skunkware distribution is available via http and ftp at either :

In addition, there is a Skunkware distribution intended specifically for the SVR5 based SCO UnixWare 7. This distribution can be accessed via either http or ftp at :

After locating a component's download directory (see the previous answer), the typical UnixWare Skunkware distribution will contain several files. These include :

A "package" file installable with the pkgadd facility on UnixWare
This is the file "component.pkg", where "component" stands for the name of the Skunkware component (e.g. vim.pkg). This is the preferred and recommended downloadable and installable component format.
A gzip'd tar or cpio archive
This file is typically named component-release.tar.gz or component-release.cpio.gz where "component-release" stands for the name and release of the component (e.g. vim-4.6). This is an alternate distribution format which is intended for those people who dislike using the pkgadd facility or for components which have not yet been packaged for use with pkgadd.

This file contains a binary distribution which can be extracted by hand as the root user from / on the target system. If a component.pkg file exists for this component, it is recommended to download that and install using pkgadd.

Source for the component
There should always be a gzip'd tar archive of the source used to build a particular Skunkware component as well as a pointer back to the original source (often they are identical). This source archive is usually stored in the "src" subdirectory of the download directory for a component. For instance, the source to vim is in the directory /skunkware/uw7/editors/vim/src. This directory (and the one at /skunkware/osr5/editors/vim/src) is a symbolic link to the single source directory that contains the source archives for all platforms. For instance, the vim source is actually located at /skunkware/src/editors/vim) and is linked into the osr5 and uw7 trees.

[top]

How do I install the VOLS.tar media images on OpenServer?

After downloading the component's VOLS.tar file (see the previous answer), login to your system as the root user, extract the VOLS.tar archive into an empty directory (say, for example, the directory /tmp/foobar) and run the "custom" command. Select the menu items "Software" -> "Install New". Select your host and, when prompted for the Media Device, select "Media Images" and "Continue". When prompted for the Image Directory, type in "/tmp/foobar or whatever is the name of the directory containing the extracted VOLS.tar media images. Select Ok and proceed.

[top]

How do I install the xyz.pkg package file on UnixWare?

After downloading the component's component.pkg file (see the previous answer), login to your system as the root user or another user with system administration priveleges. Change directory to the location of the downloaded component.pkg file and run to following command : 

    # /usr/sbin/pkgadd -d `pwd`/component.pkg all
where "component" stands for the name of the downloaded component.

[top]

What now? Where is the application I just installed?

Basically, we've tried to confine the Skunkware applications and their associated data files, libraries, and such to /usr/local. The binary executables get put in /usr/local/bin, the man pages in /usr/local/man, the libraries in /usr/local/lib, the header files in /usr/local/include, and so on (with some exceptions).

So, to be able to execute something like, say, gzip, you would either need to : 

    $ /usr/local/bin/gzip ...
or, preferably : 
    $ PATH=$PATH:/usr/local/bin
    $ export PATH
    $ gzip ...
You can add /usr/local/bin to your shell PATH variable by editing your $HOME/.profile (this variable is called path for csh users and can be set in the $HOME/.login).

For Bourne and Korn shell users (sh and ksh), add the following lines to your .profile : 

    PATH=$PATH:/usr/local/bin
    export PATH
For C-shell users (csh), add the following to your .login : 
    set path = ($path $home/bin /usr/local/bin .)
You can also add /usr/local/man to your MANPATH variable in a similar manner.

After setting up your PATH (and MANPATH) as described above, you can then execute binaries that live in /usr/local/bin by just typing their name (e.g. gzip). If you setup your MANPATH as well, you can read man pages that live in /usr/local/man by simply typing "man command" where "command" is a command like gzip or whatever.

[top]

What "web development" tools does Skunkware contain?

Skunkware also contains a number of useful web development tools. I'll briefly list a few and you can find out more by following the links to the respective home pages.

This is not a comprehensive list - just off the top of my head.

I have found the following fairly useful :

[top]

How can I contribute software to SCO Skunkware?

Contributions to SCO Skunkware are welcome. If you have ported something which you consider valuable and/or interesting and would like to have it included in the Skunkware distribution, send e-mail to skunkware@sco.com describing the component and how the Skunkware team can download the source and compiled binary distribution. Please also include a README or ReadMe.html document describing the component, author, porter, testing, build instructions, documentation, where to retrieve the original source, home page for the component, and other relevant information.

If you do not have an ftp or web site which can be used to access the contribution, the Skunkware team can provide you with instructions for uploading your contribution to ftp.sco.com.

[top]

What if I find a problem with an SCO Skunkware component?

Please e-mail any problems you discover with SCO Skunkware to skunkware@sco.com describing the component which exhibits the problem, where and when you downloaded the component, how the component was installed, base operating system environment on which the component is running, and enough specific details of the problem for us to be able to duplicate it. A minimal test case which provokes the problem is helpful.

If you cannot provide all of the above, simply e-mail us with whatever information you have and we will attempt to provide a fix as quickly as possible.

[top]

How much does SCO Skunkware cost?

SCO Skunkware is free. It is distributed freely via our ftp and web sites and the CD-ROM is distributed freely at trade shows, conferences, training centers, and other venues. The company that does our on-line ordering system will be charging $10 dollars per CD-ROM to cover the costs of shipping, handling and media. If you cannot afford $10, e-mail skunkware@sco.com requesting a free copy.

[top]

Can I give SCO Skunkware away for free?

Yes. If you are running a training center or would otherwise like to redistribute SCO Skunkware for free, please contact us at skunkware@sco.com and indicate how many copies you would like. There may be a charge for bulk orders to cover the cost of media, shipping and handling.

[top]

Can I charge money for SCO Skunkware?

No. SCO Skunkware is a Trademark of The Santa Cruz Operation, Inc. and may not be resold. Further, most of the SCO Skunkware components are restricted by copyright which prevents their sale or inclusion in a commercial product. See the individual COPYING or README files for a component for specifics with regard to licensing and redistribution of that component.

[top]

Which Skunkware components are intended for platform XYZ?

The Skunkware team has tried to clearly divide the Skunkware components into packages intended for specific SCO operating environments. The top-level Skunkware directory (on the CD-ROM, ftp site and web site) has subdirectories named :

osr5
this directory contains software for SCO OpenServer 5
uw2
this directory contains software for SCO UnixWare 2.x
uw7
this directory contains software for the SVR5 based SCO UnixWare 7
Most of the software intended for SCO UnixWare 2.x will install and run perfectly well on the SVR5 based UnixWare 7. The OpenServer Skunkware packages should also run on the SVR5 based UnixWare 7 but have not yet been tested in this environment.

[top]

Where can I find audio tools for use with my SCO system?

You can download the latest players and drivers and such at http://www.sco.com/skunkware/audiovis/index.html

In particular, the Open Sound System audio drivers for SoundBlaster compatible cards are available at http://www.sco.com/skunkware/osr5/audio/oss/ for SCO OpenServer and http://www.sco.com/skunkware/uw2/audio/oss/ for SCO UnixWare 2.x.

Another good source for audio tools is 4Front Technologies at http://www.4front-tech.com/ossapps.html

Finally, one of the applications we tested with the Linux emulator, lxrun, was the Linux RealAudio player. So, an additional reservoir of audio tools resides in the Linux audio applications in conjunction with lxrun on SCO OpenServer. The download area for lxrun is : http://www.sco.com/skunkware/osr5/emulators/lxrun

[top]

I'm having a problem playing audio.

If you are using the Open Sound System audio driver included with Skunkware 97, check /usr/lib/oss/soundon.log to make sure everything got initialized properly. A common problem is simply not having run the "soundon" utility. On my system i have created a startup script /etc/rc2.d/S95soundon containing : 

case "$1" in
start)
    /usr/lib/oss/soundon
    ;;
stop)
    /usr/lib/oss/soundoff
    ;;
*)
    exit 1
esac
You can also check /usr/lib/oss/install.log to see if there were any errors during installation.

For a list of device nodes and their major and minor numbers, take a look in /usr/lib/oss/modules/sndb/Node. You can create any missing device nodes with the /etc/mknod command.

If this still doesn't work, you might try using "trace" on play_snd to try and see exactly what device node it is trying to open.

If you are completely stumped, e-mail skunkware@sco.com with a problem report and the contents of the above mentioned log files.

[top]

Are the free Open Sound System audio drivers crippled?

The reason 4Front is still charging $40 for copies of the driver is that they are selling the non-SoundBlaster drivers. SCO only licensed the drivers for true SB and 100%-compatible cards.

Note that there are some cards that call themselves "SoundBlaster compatible" but aren't. These cards have an 8-bit SB-lookalike mode, but it takes special instructions to put the card in SB compatability mode. These cards are not supported by the drivers SCO licensed, but are supported by other drivers from 4Front.

Also, some of the more advanced SB cards (like the AWE64) come with an Emu8000 synthesis chip. These also require a special driver from 4Front.

The drivers that SCO licensed for inclusion in the OS (and that were on Skunkware) will do the following:

Each of the above bullets corresponds to a separate driver. (If you have an OSR5 system with the 4Front drivers from Skunkware installed, you can look in /usr/lib/oss/modules and see the individual drivers.)

Anyway, there's no such thing as a driver that's crippled so that "PnP cards don't work". Even with the old Voxware drivers, you can use a PnP sound card if you have a Plug & Play BIOS to activate the card.

[top]

Where can I find Skunkware for SCO ODT / SCO UNIX 3.2v4?

All of the previous releases of SCO Skunkware are still on-line and accessible via either ftp or http at :

ftp://ftp.sco.com/Skunk1
Skunkware for SCO ODT and SCO UNIX 3.2v4 systems
ftp://ftp.sco.com/Skunk2
The SCO Skunkware 5 release for SCO OpenServer systems (vintage 1995)
ftp://ftp.sco.com/Skunk96
The SCO Skunkware 96 release for SCO OpenServer and SCO UnixWare systems (vintage 1996)
http://www.sco.com/skunkprev/index.html
HTTP gateway for all previous SCO Skunkware releases

[top]

What if I can't locate the component i am looking for?

If you cannot find what you are looking for, e-mail skunkware@sco.com with a request for information on the desired software.

[top]

When I run the xyz program i get an error something like :
"dynamic linker: xyz: cannot open /usr/local/lib/libxyz.so" .

This can very likely be remedied by installing the Graphics Libraries package for your platform.

For UnixWare 7 systems, this package can be installed by issuing the command (with owner priveleges): 

    # pkgadd -d /dev/cdrom/c1b0t0l0 glib
(the exact device node may vary from system to system)
or by mounting the Skunkware 7 CD-ROM and issuing the command: 
    # pkgadd -d <mount-point> glib

For SCO OpenServer, this package is available at http://www.sco.com/skunkware/osr5/libraries/Glib/. If you have the Skunkware 97 CD-ROM, you can install this component (as root) by cd'ing to /osr5/lib/Glib and running the shell script "./Install". This script just runs the command : 

custom -p SKUNK97:Glib -i -z `pwd`/archives/TAPE

For SCO UnixWare 2.x, there are several individual packages available in the subdirectories at http://www.sco.com/skunkware/uw7/libraries/. If you have the Skunkware 7 CD-ROM, you can install individual components of the Graphics Libraries package (as root) by cd'ing to /uw2/Packages and running the pkgadd program on the appropriate pkg file(s) in the subdirectories there.

The programs that use these libraries were built to look in /usr/local/lib for the necessary files. It is possible that a program was built incorrectly. If you already have the Graphics Libraries installed and are still getting an error message like this, you may need to create symbolic links from the appropriate libxyz.so in /usr/local/lib to /usr/lib. If this is the case, please e-mail skunkware@sco.com with the name of the program exhibiting the problem.

[top]

Where can i find u386mon for SCO OpenServer ?

The u386mon README is at :
http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/README.html

The u386mon and nlsym binaries are available via either :
http://www.sco.com/skunkware/osr5/bin/
or
ftp://ftp.sco.com/skunkware/osr5/bin/

The binaries need to be "setgid mem" : 

    # chgrp mem u386mon nlsym
    # chmod 2755 u386mon nlsym
First, run nlsym as root.

You should then be able to run u386mon as a normal user. Of course, you can restrict permissions if you like.

The source for u386mon is available via :
http://www.sco.com/skunkprev/osr5/CD-ROM/src/Tools/u386mon-2.74/

[top]

Where can i find answers to questions programmers might ask about developing on SCO platforms ?

The following links refer to SCO newsgroups that contain a wealth of information. They are vehicles to use for discussing various SCO topics with developers, service providers, resellers & distributors, and other SCO community members.

These links rely on your browser's ability to open a news reader and the news reader being properly configured to access a current news feed.

If your browser can't open a news reader, you don't have access to a current news feed, or if you just prefer to read news articles with your browser, an alternate way to read news is by accessing Deja News at the following URL:

Developer FAQ Links:

[top]

What if my question isn't answered here?

If you have a question that is not covered by this FAQ, e-mail the Skunkware FAQ maintainer, rr@sco.com, with your question.

[top] 

Revision Information
--------------------
Version:  1.4
Date:     02 Jan 1998
Author:   Ronald Joe Record
          rr@sco.com

Last Updated: Friday Mar 19, 1999 at 13:23:00 PST

  © Copyright 1997 The Santa Cruz Operation, Inc. All rights reserved.