This site contains information intended to be helpful.


Most of it is Unixish, so some of what you'll find here is useful if you are running Unixware, Solaris, Linux, Mac OS X or whatever, but if your specific OS is not specifically mentioned, take whatever you read as being POSSIBLY WRONG FOR YOU. If you are in the Mac OS X or Linux or whatever sections, what you are reading might be useful if you are running BSD , but you needv to be careful. That previous sentence has a good example of why: I left the "needv" typo in to illustrate a point: I and the other people who have put articles here are just human beings. We make mistakes. The mistakes may not be as obvious as that, or might just be errors of understanding.

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

I am a Kerio reseller. Articles here related to Kerio products reflect my honest opinion, but I do have an obvious interest in selling those products also.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.

Originally, this was a "SCO Unix site". Or so the title page said, anyway. However, that wasn't really ever true, because I've been interested in Linux and other Unix-like OSes for years. There's also a lot here that isn't necessarily strongly Unix: it's just computerish or techy. I also write a little about Windows. But you will find quite a bit here that is SCO Unix related.

In general, you need to be very careful when applying any suggestions or ideas gleaned from this or any site. First, there may be typos or even actual errors in what you read. Secondly, software changes all the time: what may have been correct a year ago may be very wrong today.

Therefor, take everything with a grain of salt and do whatever you can do to confirm that whatever you are about to do is appropriate and not dangerous. If you aren't confident that you can do that, please find someone with more knowledge and rely on their judgement.

Program code on this site is particularly dangerous for unsophisticated users, and should never be used unless you fully understand it. Most code published here is intended to be illustrative rather than functional.

Some material here is quite old and therefor may be outdated. How do you know what's old? Everything within the past few years has a copyright notice at the bottom; if there is not one, what you are reading is older than 1997. I do try to revisit these articles and make notes about things that have changed, but I don't always get to everything.

What should concern you the most is that a lot here was written before many of us gave much thought to security. Nowadays, I'm paranoid about that, and scrub user input religiously, usually try to avoid it entirely, etc. But older stuff here isn't, and even newer stuff may not mention security as much as it should. It is something you need to worry about today.

Why does this site exist? I suppose we all have our own reasons for contributing. In my case, it's the "pay it forward" idea: I learned a lot from other people, particularly from Usenet, and I want to pay for that.

I'm also driven because I never found any of this stuff easy. Still don't. Man pages are often of little help, and while Google certainly makes it better than it was when I started playing with this stuff (1967), it can still be very hard to find resources that explain what you want in a way you can understand.

Part of the problem is those lucky folks who do find it all so easy. For them, it's all trivial, it all makes instant sense. They say "RTFM" or "use the source, Luke" because that's all they need. Not all of them are like that, of course: some of the uber-geeks have real patience with us mere mortals and do get down on their knees to help us tie our shoelaces. But so often they don't explain the one thing we really don't get, because they just never had any problem with that part - it was too trivial. And that's where I try to help: I feel the pain of not understanding because so often I struggle to understand. When I write about something I now do understand, I try hard to remember the things that blocked me when I didn't, and try to explain them. I don't always succeed, of course, but those are my intentions.

So I post to Usenet, and I put articles and other stuff on my web site. The guru's and super-geeks will find my stuff naive and sometimes wrong (and of course I correct it then), but a lot of ordinary folks may get a little help now and then. That's why I make the effort.