Skunkware 98 Release Notes

Welcome!

. . . . . . . Skunkware 98 Release Notes

What is it ?
Getting started
Accessing on other platforms
Source Code Distribution
Technical Library Supplements
Default package configurations
Known limitations and problems:

SCO Skunkware is the generic name for a free collection of software prebuilt for SCO systems. This distribution is Skunkware 98 and is targeted mainly at the SCO OpenServer platform. To obtain SCO Skunkware pre-built for use on UnixWare, see the SCO Skunkware Web Site or you may wish to order the Skunkware 7 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://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 software on the Skunkware 98 CD-ROM is licensed under a variety of terms. Much of it is licensed under the terms of the GNU General Public License. Some is licensed under the GNU Library General Public License. Other components are licensed under the Artistic License. Many of the components are "freeware" with no restrictions on their redistribution while a few components are "shareware" meaning the author would like you to try the software and, if you wish to use it, send her some money. A few components are commercial products which can be used freely for non-commercial purposes (e.g. msql). Some components simply restrict their use to non-commercial purposes.

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 98 Software Categories
audio	emulators	libraries	shellutil	fileutil	mail	sysadmin	db	net
textproc	devtools	interp	news	video	editors	lib	shells	www
X11 Graphical Categories
apps	fonts	games	graphics	misc	savers	utils	viewers	winman

Many of the components of SCO Skunkware may be viewed as productivity and development tools to be taken seriously. Don't let its whimsical nature fool you. Examples of serious tools on Skunkware 98 include:

The GNU C Compilation system
Mtools - DOS filesystem manipulation tools
Scripting languages (Tcl, Tk, Python, Expect)
Internet/Network tools (apache, squid, xdir, ldap, many more)
Editors and text processing tools (xcoral, xemacs, ghostscript, vim, xhtml)
Many many more

Of course, Skunkware also contains fun stuff. Gotta have something to keep the polecats entertained thru the night. Examples include:

Games (xdoom, xgalaga, xboing, xpool)
Graphics (mathematical recreations, animation viewers, image manipulators)
Audio (audio players and editors, mixers, CD players, games with sound)
Stuff (view astrology charts, graphical fish tank, lots more)

Several of the components on this CD should be considered experimental. Consider Skunkware a research tool. Examples:

Egcs, the Experimental GNU Compilation System from Cygnus.
Alpha or pre-release versions of window managers and graphical tools
A variety of Java classes and applications from Acme Laboratories
VRwave, a Java based VRML 2.0 browser
Endo, a tool for exploring dynamical systems in the plane

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@sco.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.

Getting Started

Mounting the Skunkware 98 CD-ROM
[Note that it is not necessary to mount the Skunkware 98 CD-ROM in order to install the custom installable packages. See the section below on installing the Skunkware 98 software.]
To mount the Skunkware 98 CD-ROM on an SCO UnixWare system, use the command:
```
    # mount -r -f cdfs /dev/cdrom/c1b0t0l0 /mount-point
```
where 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 (the exact name for the cdrom device is usually the only entry in /dev/cdrom).
On an SCO OpenServer Release 5 system issue the command:
```
    # mount -r /dev/cd0 /mount-point
```
Making room for the Skunkware 98 software
The installation of all the Skunkware 98 components requires about 500 MB of free space on the root partition (/opt/K/SKUNK98). If your root partition does not have sufficient space, or you wish to utilize an alternate filesystem for the Skunkware 98 components, prior to installing Skunkware 98 create a symbolic link in /opt/K as follows:
```
        # mkdir /u/skunk98
        # cd /opt/K
        # ln -s /u/skunk98 SKUNK98
```
The above commands assume a separate /u filesystem with sufficient disk space. The exact name of the alternate filesystem mount point is system dependent.
You may also wish to place your /usr/local file hierarchy on a separate filesystem. To do so, create the appropriate symbolic link - e.g.
```
    # ln -s /u/local /usr/local
```
Installing the Skunkware 98 Software
The installation of all the Skunkware 98 components requires about 500 MB of free space on the root partition for OpenServer (/opt/K/SKUNK98).
After mounting the Skunkware 98 CD (mount -r /dev/cd0 /mnt), as root run the command:
```
    # /mount-point/INSTALL
```
The 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 (/etc/custom).
Alternatively, an interactive graphical installation can be performed by running the Software Manager (/etc/custom) as root. Select "Software" -> "Install New". If your Skunkware CD is inserted in the local CD-ROM drive, install from the local host and select the appropriate CD-ROM drive as the Media Device.
After the Software Manager has read the Skunkware product database, you can select which components you wish to install or choose to install the full product (see notes above on disk space considerations).
NOTE: A full installation of SCO Skunkware 98 will consume over 500 Megabytes of disk space and take a couple of hours.
To install an individual package, execute the command:
```
    # custom -p SKUNK98:default:Package -i -m /dev/rcd0
```
where "Package" is the name of the desired component. See the file /mount-point/osr5/COMPONENTS for the list of available components.
Installing the Open Sound System audio drivers
1. You should remove any audio drivers you currently have installed. The important thing is that you remove them from the kernel. If you have an older copy of the OSS drivers installed, you may be able to remove them from the kernel by running "/usr/lib/oss/Remove". On a different note, the SCO PnP driver should be enabled. If you had an older version of the OSS drivers, the SCO PnP driver might have been disabled. The file "/etc/conf/sdevice.d/PnP" should contain a line like so (with "Y" in the second field):
```
	PnP	Y	1	0	etc. etc....
```
  while /etc/conf/sdevice.d/pnp should have "N" in the second field, if that file exists. If not, make the appropriate changes, rebuild the kernel with:
```
	/etc/conf/bin/idbuild
```
  and reboot.
2. Run "scoadmin isa" or "/etc/pnp" (should be the same thing) to do plug-and-play configuration if your card is plug-and-play. If you don't know whether your card is plug-and-play, you can find out by running this command. If you see your card listed, it's plug-and-play. If not, it's not. If it is plug-and-play, make sure it is configured and make note of the resources it is configured to use. At this point, the resources must be re-entered manually in the audioconfig utility.
3. Run "/usr/lib/audio/audioconfig/audioconfig". Choose the "add card" button. Choose your card or, for plug-and-play, choose "autodetect". Enter the appropriate resources for your card, and press okay.
4. If you have problems, email skunkware@sco.com. Otherwise, reboot and test the soundcard. One way to do that is to re-run the audioconfig program and use the "test" button. Alternatively, find a .au file and "cat myaufile.au > /dev/audio".
NOTES:
1. This is an early availability release of the OSS audio drivers. For subsequent releases, check http://www.sco.com/download/.
2. You must do the plug and play configuration as a separate step before running audioconfig, as described above (if you have a PnP card, that is).
3. Once the soundcard is configured, it is not active until you reboot. So, for example, don't bother clicking the "test" button until you reboot. :)
4. The audioconfig utility will display some stuff in the xterm while it is running. This is for debugging purposes and will help me figure out what is wrong if you run into trouble.
Configuring your system for use with Skunkware 98
If, as root, you are running the X.Desktop, then you can configure your system to mount the SCO Skunkware 98 CD-ROM by double-clicking the System Administration folder -> Filesystems -> Filesystem Manager. Alternatively, at a root shell prompt, type "scoadmin f" to bring up the Filesystem Manager. Next select Mount -> Add Mount Configuration -> Local and enter /dev/cd0 for the device and a mount point. Change the "Can Users Mount" to Yes and uncheck the "At System Startup" mount. After completing this operation, you should be able to mount and unmount the SCO Skunkware 98 CD-ROM by typing "mnt mount-point and "umnt mount-point as any user.

After completing the installation of the Skunkware 98 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 98 shared libraries have been built with the appropriate flags.
Browsing the Skunkware 98 HTML Documents
For an introductory tour, point a web browser at /mount-point/index.html
```
    # /usr/bin/X11/netscape file:/mount-point/index.html
```
If you do not have Netscape Navigator installed, download a trial copy from http://www2.sco.com or (for OpenServer) install NCSA Mosaic off of this CD:
```
    # custom -p SKUNK98:default:Mosaic -i -m /dev/rcd0
```
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 install Lynx 2.7.1 (a character browser) off of this CD (OpenServer only, if you are running UnixWare 7 then Lynx is included by default).
```
    # custom -p SKUNK98:default:Lynx -i -m /dev/rcd0
```
Then execute the command:
```
    # lynx file:/mount-point/index.html
```
SCO Skunkware 98 contains files suitable for installation on SCO OpenServer systems with the Software Manager facility (/etc/custom). In addition, there are compressed archives of pre-compiled utilities which can be extraced manually. Finally, there are hundreds of source archives (almost everything on the CD is accompanied by the source used to build it).
Removing the Skunkware 98 software
On SCO OpenServer systems, use the Software Manager (/etc/custom) to remove Skunkware 98 components. This can be done interactively by running custom and selecting the component(s) you wish to remove, or non-interactively by issuing a command like the following:
```
    # custom -p SKUNK98:default -r <package-list>
```
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.
Source Code Distribution
In almost all cases, source code is also provided, 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://www.sco.com/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 gzip-compressed tar or cpio format. In order to extract these, use the command:
```
    $ gzcat /mount-point/src/<directory>/<package>.tar.gz | tar xf -
```
or, in the case of a compressed cpio archive:
```
    $ gzcat /mount-point/src/<directory>/<package>.cpio.gz | 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 gzcat installed (part of the gzip package), you can install it off of the SCO Skunkware 98 CD via the command:
```
        (OpenServer systems)
        # custom -p SKUNK98:default:GZIP -i -m /dev/rcd0

        (UnixWare 7 systems)
        # pkgadd -d /mount-point/uw7/gzip.pkg

        (UnixWare 2.x systems)
        # pkgadd -d /mount-point/uw2/gzip.pkg
```
Technical Library Supplements
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 98 packages have been pre-configured (with the exception of xmcd which will prompt you for your CD-ROM make and model; and inn which may prompt for a "news" user password).
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:
- The Apache web server is configured to run on port 8080. If you are not going to use Squid as an httpd accelerator, you may wish to run the Apache web server on port 80. To do so, modify /usr/local/lib/apache/etc/httpd.conf. Further, the default document directory for the Apache web server is set to /usr/local/lib/apache/share/htdocs. If you wish to serve your HTML documents out of a different location, modify /usr/local/lib/apache/etc/srm.conf and /usr/local/lib/apache/etc/access.conf
- The Squid Internet Object Cache is configured to run on port 80 and to act as an httpd accelerator for the server running on port 8080 (by default, the Apache web server). If you wish to use this default configuration, remember to stop/disable any other server running on port 80. In particular, the Netscape FastTrack server is usually configured to run on port 80.
- Skunkware 98 contains a custom installable integrated GNU compilation system. This includes both the Free Software Foundation's GNU C Compiler and Cygnus' experimental GNU C Compiler (EGCS). The file /etc/default/gcc can be used to specify which is the default preferred compiler. The entries in this file set the system-wide default. An individual user can override this default by setting and exporting the PREFERRED_GCC environment variable. This variable must be set to either /usr/local/lib/front-fsf or /usr/local/lib/front-egcs. If set incorrectly, the system will revert to the preference specified in /etc/default/gcc.
- Several packages install documentation, manuals, tutorials and other introductory and informative matter as HTML documents in /usr/local/man/html. During the installation of these packages, a symbolic link is created in the default Apache web server document root. Thus, the documentation for these packages can be accessed via a browser. For instance, the HTML documents describing the Xcoral editor are installed in /usr/local/man/html/xcoral. A symbolic link pointing to this location is installed as /usr/local/lib/apache/htdocs/docs/xcoral. Thus, to access the Xcoral HTML documentation, you need only open the URL http://your.server.name/docs/xcoral/ These convenience links are provided for Count, SmallEiffel, addressbook, crossfire, gd, giftrans, gimp, git, gv, GNU history, Hypermail, jasmin, klassmaster, lxrun, mathrec, msql, mutt, mysql, nedit, omniORB, php, GNU readline, sox, squid, tcsh, vrwave, wget, wwwtar, xacc, xcoral, xtar, xtide and xv.
- If you mount the CD-ROM under your default document root, you will be able to serve up the Skunkware 98 HTML documents with your web server. For instance, after installing the apache and squid packages, if you mounted the Skunkware 98 CD-ROM on /usr/local/lib/apache/share/htdocs/skunkware, then opening the URL http://your.server.name/skunkware/ would allow you to browse the contents of the Skunkware 98 CD-ROM from any browser that could access your server.
- The INN installation is configured to install many of its files owned by the user "news" and group "news". During the inn package installation, this user/group is created if it doesn't already exist. If the installation creates a "news" user, you will be prompted for a password during installation.
- The Xmcd (Motif audio CD player) package will prompt you for the CD drive configuration during the installation. If you wish to configure Xmcd during the installation, you should know the make and model number of your CD drive(s).
- The Netpbm suite of graphical file conversion utilities are in the Glib package. In order to install these utilities, issue the command:
```
    # custom -p SKUNK98:default:Glib -i -m /dev/rcd0
```
  They are installed in /usr/local/bin. The Glib package is installed either during a full installation of Skunkware 98 or as part of the "Development Tools" software set.
- Additional Perl modules will be available via http://www.sco.com/skunkware/osr5/interp/perl/. These include various database interfaces, ImageMagick enhancements and more.
- Perl 5.005 installation - Skunkware 98 contains a custom installable Perl 5.004_04 distribution as well as a gzip'd tar archive of a Perl 5.005 binary distribution. In order to install Perl 5.005, insert the Skunkware 98 CD in the CD-ROM drive and execute the following (as root):
```
    # custom -p SKUNK98:default:Perl -r
    # mount -r /dev/rcd0 /mnt
    # cd /
    # gzcat /mnt/osr5/interp/perl-5.005/perl-5.005.tar.gz | tar xf -
    # umount /mnt
```
  You may also wish to create a link from /usr/local/bin/perl to /usr/bin/perl. Note that gzcat is in /usr/local/bin.
- Alternate window managers' default configurations are those provided in the source distributions and will need to be tailored for use on OpenServer 5. That is, the rc startup files for fvwm, fvwm95, AfterStep and WindowMaker may need system-specific configuration. The Skunkware team plans on making OpenServer specific window manager configuration files available via the Skunkware web site at http://www.sco.com/skunkware/x11/winman/.
- Individual account configuration of WindowMaker must be done prior to using the WindowMaker window manager. To do so, login as the user who desires to use WindowMaker and run the WindowMaker configuration script:
```
    $ /usr/local/bin/wmaker.inst
```
  When prompted for the name of the initialization file to use, enter .startxrc
- XBuffy default mailboxes are set in the file /usr/lib/X11/app-defaults/XBuffy. In order to get xbuffy to monitor your personal mailboxes, you will need to add a line similar to the following to your $HOME/.Xdefaults :
```
*mailboxes:     /usr/spool/mail/wfp:/home/wfp/.mailbox:/home/wfp/nsmail/Inbox
```
  replacing the user name wfp with your own.
Known Limitations and Problems
- A full installation of the SCO Skunkware 98 media images for SCO OpenServer requires approximately 500 Mb of disk space. If your system's root filesystem does not contain sufficient disk space (a check is performed at the beginning of the installation), then you may wish to perform the following workaround (rather than removing files from the root partition):
```
      # cd /opt/K
      # ln -s /u/local local
```
  Where /u/local resides on an additional disk with sufficient space.
- Prior to installing the Mini SQL relational database management system, it may be necessary to shutdown any existing mSQL daemon running on port 1114. To do so, issue the command:
```
    # /usr/local/Hughes/bin/msqladmin shutdown
```
- The LDAP slurpd program is not included in Skunkware 98. Slurpd is the database replication program for the ldap server.
- Some programs - including the xfishtank animated background and the xgrabsc command - may need a PseudoColor visual. Before attempting to run either xfishtank or xgrab, the front-end for xgrabsc, you may need to configure your X server to run in 256 color mode. Sorry.
- On OpenServer 5.0.4 and earlier there may be no /var/tmp directory. Some Skunkware components (e.g. nvi) may attempt to use this directory for temporary files. A /var/tmp directory can be created as follows:
```
    # ln -s /usr/tmp /var/tmp
```
- Alternate window managers - The Skunkware 98 window managers (Fvwm 2, AfterStep, WindowMaker, Kde) should be considered experimental. Of the four, Fvwm 2 is the most stable and well tested. Some color-intensive X clients may not be able to allocate sufficient color cells, particularly with WindowMaker. Additional window managers and updated versions of these will be available at the Skunkware web site.
- The K Desktop Environment (KDE), release 1.0, was added to Skunkware 98 at the last minute. KDE installs in the /usr/local/kde directory. Very little testing of kde was possible. Documentation for KDE can be found at the KDE web site and in the Skunkware 98 installation of KDE at http://localhost/docs/kde (assuming you have installed KDE, Apache and Squid).
  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/
  It is hoped that this remarkable new desktop environment will please the graphical Skunkware 98 user.
- Exiting the alternate window managers does not always exit the X session and return you to the graphical login. If this happens, switch to another screen (ctrl-alt-fkey) and kill the X server process for your display:
```
    # ps -ef | grep X
    # kill <pid>
```
- Exiting Midnight Commander under WindowMaker can be difficult as the WindowMaker window manager grabs F10.
- Xboing minimum height exceeds that of an 800x600 display. To play xboing effectively, the screen resolution must be set larger than a 600 pixel height.
- Adding freefont directory to your font path can be accomplished with the following commands:
```
    $ xset -fp /usr/local/share/fonts/freefont
    $ xset +fp /usr/local/share/fonts/freefont
    $ xset fp rehash
```
  The gimp command has been wrappered with a shell script which does this for you.
- The SCO OpenServer 5 man command expects the man pages to be in directories named man.suffix and cat.suffix. Many public domain packages place their manual pages in directories like man1, man8, cat1, cat8 and so on. Further, these directories are usually located in /usr/local/man rather than /usr/man. To remedy this, add /usr/local/man to your MANPATH (see /etc/default/man) and create symbolic links from mann to man.n, catn to cat.n and so on.
- Xdoom needs -nosound argument if no audio. If the OSS audio driver is not installed, in order to run the Xdoom video game you will need to invoke it with the "-nosound" argument. For instance:
```
    $ xdoom -nosound
```
- The "makecd" package is only known to work on SCO OpenServer 5.0.4 with the HP SureStore 4020/6020 or Philips CDD 2600 CD-ROM writers.
- On OpenServer, if you use g++ to link an ELF binary, libg++ and libstdc++ will be linked in automatically, regardless of whether they are actually used by your program. Such binaries will not run on machines that do not have the libg++ and libstdc++ shared libraries installed. If you know your program does not need these libraries, you can link it using gcc and they will not be included. In programs that do use libg++ or libstdc++, you can maintain portability by using the "-static" flag which makes a statically-linked binary.
- Endo default window sizes may appear too small. Although the pre-configured scripts in /usr/local/mathrec/endo do create correct window sizes, invoking the endo program with no arguments may create windows with a minimum height. If this is the case, simply enlarge the window(s) by clicking on and dragging the window border(s).
- Apparently xlincity needs a pseudo-color visual. That is, if you have configured your video for use with more than 256 colors, xlincity fails with "Major opcode of failed request: 89 (X_StoreColors)". If you find you can run xlincity in TrueColor mode, let us know.
Comments
We are interested in your general comments about this distribution and about development tools in general. Please feel free to e-mail skunkware@sco.com with comments, criticisms and suggestions.

Ronald Joe Record SCO rr@sco.com

Senior Engineer for Free Stuff, Skunkware, technical tools, etc.

400 Encinal St. Santa Cruz, CA 95061 FAX: 408-427-5417 Voice: 408-427-7604

Dion L. Johnson II SCO dionj@sco.com

Product Manager for Free Stuff, Skunkware, technical tools, etc.

400 Encinal St. Santa Cruz, CA 95061 FAX: 408-427-5417 Voice: 408-427-7565

Last Updated: Friday Mar 19, 1999 at 09:56:46 PST

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

Ronald Joe Record		SCO	rr@sco.com
Senior Engineer for Free Stuff, Skunkware, technical tools, etc.
400 Encinal St.	Santa Cruz, CA 95061	FAX: 408-427-5417	Voice: 408-427-7604

Dion L. Johnson II		SCO	dionj@sco.com
Product Manager for Free Stuff, Skunkware, technical tools, etc.
400 Encinal St.	Santa Cruz, CA 95061	FAX: 408-427-5417	Voice: 408-427-7565

. . . . . . . Skunkware 98 Release Notes

Table of Contents