![[ TABLE OF CONTENTS ]](../gx/indexnew.gif)
![[ FRONT PAGE ]](../gx/homenew.gif)
The fifth International Linux Congress was held June 3-5, 1998, at Cologne University in Germany. This was only a few days after the Linux Expo held at Duke University in North Carolina, U.S.A. (May 28-30), which made for a few tired participants including some of the speakers who attended both events. On the first day of the Congress, intensive tutorials on various subjects were offered in both English and German. These included ``Becoming a Debian Developer'' by Bruce Perens, ``KDE Programming'' by Kalle Dallheimer and Matthias Ettrich, and ``ISDN4 for Users'' by Klaus Franken.
The talks began the next day, opening with the keynote speaker, Jon ``maddog'' Hall. Jon's talk, entitled ``Economics of Computing for the 21st Century'',day, opsearch utilities for your site, depending on whether you are using SiteWrapper, WebPost or neither. Chapter 13 covers the AddaLink tool for creating and maintaining a hot list of links. Chapter 14 covers QuickDB, a simple text-based database engine with a browser interface for adding, editing and deleting entries.
Chapter 15 presents a Bulletin Board utility, and also discusses using FrontPage for a Discussion Board. Chapter 16 takes the next step by covering a couple of freely available Chat programs.
Chapter 17 provides a couple of search engine agents, one to submit a URL to a multitude of search engines and two more which report your location on the search engines. The final chapter presents BannerLog and ClickThru, tools which track and log click-throughs and page views of banner ads on your site.
I set up a dummy site on my Linux box for installing and trying out a few of the provided utilities. The installation instructions in each chapter are divided into UNIX and NT sections and are relatively simple to follow. However, some unfortunate problems arose.
There are .zip files for each package, and non-zipped directories for each of the packages on the CD-ROM. A mild inconvenience is that some of the .zip files were created with extraneous path information included, and the individual files in the non-zipped directories are riddled with ^M characters. The author has created a web site where you can find problem reports and corrections, and ``cleaner'' versions of the source files for downloading. The site is located at http://www.world-media.com/toolkit/.
Another inconvenience is that every Perl script must be checked (and possibly edited) for the proper path to Perl on your system, there is no script provided to automate this task, although writing one would be trivial for any experienced Perl programmer. Note that even if the first script you examine has the proper path, others definitely will not--so you must check and edit those with the incorrect path for your system.
More serious problems arise with the Perl code. None of the open calls for reading and writing files are consistently checked for success or failure. You'll first notice a problem when you install the SiteWrapper package and try to change the color scheme of your site with the included SiteColors program. The installation guide omits mentioning that your server will need write access to the tagfile.dat file where the color scheme is stored. Since the program does not check the return value of the open call, it will fail silently, your color scheme will not be updated and no error will be present in your server's logs. I'd seriously recommend locating all calls to the open function in all .cgi scripts and adding at least a ||die "$!"; statement to those that don't have it.
Other deficiencies with the Perl scripts are that they are not -w clean (for warnings), won't compile with the ``strict'' pragma, do not use -T for taint checking and use the older cgi.pl library rather than the CGI.pm module for Perl 5.
Even with the above comments and concerns, the packages are, for the most part, easy to install and get working. Installation and configuration of the basic SiteWrapper package took less than an hour, including time spent checking and cleaning the source code and creating simple header and footer files and a couple of dummy pages. When using this system, every page is served from a CGI program, even essentially static pages. This method allows for a great deal of flexibility and a centralized configuration style of management, but could become costly in terms of server load if your site is large or heavily trafficked.
I had a little more trouble getting the WebPost system running properly, mainly because I chose to set it up in a subdirectory of the SiteWrapper directory and a few issues were involved in getting the two packages to play nicely together. Once it was set up, however, it worked as advertised. While I found parts of the interface to be a bit clunky for creating web pages, it is a functional way to create and edit pages remotely using a browser.
Other tools were less problematic to install, Trakkit for example--I was tracking and logging myself within a few minutes of unpacking the package.
On the whole, if you are looking for instant ``shrink-wrap'' automation software with point-and-click setup and configuration, you'll be disappointed. However, typical Linux users accustomed to file-based configuration should have little trouble with these tools, especially if they already have some experience with Perl programming. The programs are not stellar examples in their present incarnation, but they can provide an inexpensive automation system for budding webmasters willing to get their hands dirty with a little Perl code. Hopefully, many of the concerns mentioned above will be addressed in a future edition.