Since Apple has continued to strongly push Mac users over to OS X, and since I never quite got the OS 9 stuff completed like I'd hoped to, I decided to remove that content when I moved to a new ISP in early 2005.   I don't plan on putting the old content back up at this time.  If there's a lot of demand for it, I might.

As for doing OS X content, to be honest, I just don't like OS X that much.  I'm enough of a technical geek that I like to be able to get "under the hood" of my operating system a bit and muck around with it.  The more I get underneath Apple's OS X hood, the more I feel like the engine's put together with duct tape and bailing wire.

A simple example to illustrate my point is this... When Apple chose a design for OS X, they based it on UNIX, which I respect as a good move.  UNIX is a mature and stable OS, and an excellent base for Apple to work with.  But instead of using a filing system that UNIX natively supports, Apple decided to graft its age-old HFS+ filing system on top of that UNIX base.  That meant the many disk-related tools and commands in UNIX needed to be modified to understand the resource forks and data forks that are a part of HFS+ files.  But Apple didn't update all the commands, just some of them.  For example, you can "ditto" a file with a resource fork and it will end up at the destination with a resource fork.  But if you use the more common UNIX command "cp" (for copy), the resource fork disappears and OS X UNIX doesn't tell you there's anything wrong/missing.  That's because Apple didn't bother to "fix" that command.  Even the excellent "rsync" backup and synchronization tool that Apple bundles in OS X doesn't understand resource forks.  If you really want to use rsync for backup, you have to download someone's "patched" or updated version of it, called RsyncX.  This is something like if Microsoft hadn't included "long filename support" in some of its command-line tools in Windows XP.  But Microsoft didn't do that.  Their command-line tools all understand long filenames, the NTFS/FAT16/FAT32 disk formats, etc., or they TELL YOU that the tool doesn't support what you're trying to do.  Apple does not take that approach, leaving the user/administrator to sort this out.  Not very customer-centric.

So while I work with OS X on a professional level out of necessity (we have a handful of die-hard Mac users who are still convinced that the Mac is the way to go), I choose not to use it at home.  I'm primarily a Windows XP and Windows 2000 Server user.  If I do choose to use a UNIX-like OS, it will more likely be the "free" Linux than the "$129/year (approximately)" Mac OS X.

Still, recognizing that there isn't a lot of good content out there for Mac OS X administrators (especially when it comes to scripting), I have added some OS X content to the site.  You can find that here.