Sorry for the lack of updates. During the time that lapsed from the previous column, my CPU died on my system. No biggie, since its under warranty, but a nuisance nonetheless. Rather than just sit on my butt and wait, I set out to install Linux on one of the machines on my desk in the office where I work as an analyst. We have no Macs in the office- its homogenous Windows NT Servers/95 clients. If there is enough interest in a followup column about integrating a Linux box into a Microsoft network, I will write about my experiences. For the moment, it bears little relevance to the subject at handÖ Suffice to say that all previous experience with the NT based network have driven me to try Linux ;)

I will, however, share with you the following observation: For those of you who have refused to use a PC (Dos/Windows) because its too cumbersome or clunky- you might as well just not bother with Linux. UNIX functions best through the command line, and its even less helpful and intuitive than the dos command line. Xwindows, while flexible and powerful, is nowhere near as mature as Windows, so you can draw your own conclusions how it compares to the Mac interface. Linux is a server architecture despite all the effort that has been made to make it more end user friendly. I expect that, with time, that it will mature to a powerful, flexible, and easy to use user OS- but not today.

In any event, while I wait for the replacement CPU, I will take the time to discuss the purposes of the server in more detail. The needs of my design office for a network server are as follows:

File Server; RIP server; Backup server; IP Router; and Fax server

Most notably absent are Web services; We are contemplating an investment in DSL to the office, but for the moment the cost is prohibitive. Until such time that high capacity permanent connection exists to our office I have little need for web services in-house, and all our web presence is currently hosted elsewhere. I will probably begin experimenting with Apache, sendmail, etc after I get the server functioning for its current purposes. Needless to say, this omission is NOT because of the lack of capability- quite the contrary. Most ISPs use Linux for all their web business.

By and large, all the solutions mentioned in this article are available for all Unix packages with some exceptions. This is remarkable, because before Linux existed, a Unix server would cost a small fortune!

Linux is remarkably well supported for an OS that isnít driven by the might of a corporate giant (Apple? Mucrosoft?!) more importantly, since its roots are 30+ years old, its is more stable and powerful, too.

A win/win situation? I still have to implement this sucker! Next issue- making a Linux Server!

I welcome all questions and comments at akoyshman@jps.net or designamics@jps.net