There's a great thread on the MacNN boards talking about removing OS X without erasing a hard drive. "Schmoo" (who may be an Apple employee; check the MacNN thread!) presented an AppleScript that can be used to easily remove all traces of OS X from a hard drive. So if you have a version installed that you'd like to remove, check out Schmoo's script in the Update soon and Applescript to Uninstall X thread.
[Editor's note: I've pasted Schmoo's AppleScript into the second part of the article; read the rest if you'd like to see it...]
If you don't like the horizontal stripes that OS X puts behind most things (menus, title bars, etc), there are now some "unlined" themes and an easy-to-use theme switcher for OS X. If you're interested in these, I'd suggest you grab them quickly, as Apple legal may not allow them to live very long.
To use, simply download the MetamorphX theme switcher, and then grab your choice of the unlined themes, launch MetamorphX and choose your stripeless theme.
I'm not sure if Apple will provide any 'official' themes for OS X or not, but here's a way to remove the stripes now if they bother you. Get 'em while you can!
The incomparable Brad Suinn from Apple has been kind enough to release juicy tidbits about the AppleShare X Client in a unauthorized readme. Amongst other things the end of the file shows how to do an AFP/IP connection using SSH so everything is nice and secure and encrypted. Check out:
I've been very upset with Epson because my fairly common Stylus Color 670 isn't supported by the distributed OS X drivers. I've contacted them a few times, and been given the same answer:"If you need to print, use Mac OS 9." So this weekend I took matters into my own hands.
The SC670 is just a renamed SC740 (which is supported) with USB. So I used textedit to find/replace the text "SC740" with "SC670" in every file inside the SC740.plugin, located in /Library/Printers/EPSON/. There were several bundles inside the plugin bundle that also needed the same treatment. I made sure to change the names of the files also.
Now my printer is recognized and prints perfectly. I'm sure there is an easier way to make the same changes using the command line, but I'm not that comfortable with many of the commands yet. Why Epson couldn't do the same thing, and add support for this printer, remains a mystery to me...
UPDATE: I received the following from the author of this tip:
"...unfortunately, it seems that it doesn't always work, and the variable may be the filesystem format. I had originally formatted my OS X partition as UFS, and when I hacked the printer driver it worked just fine.
Last night I decided to reformat the partition and reinstall OS X. This time I used HFS+. When I copied my hacked driver back to the Epson folder, it didn't work. I figured it may have been damaged in the backup/restore, so I went ahead and re-hacked the file. That didn't work either. I don't know what is going wrong. It may be because HFS+ is saving some sort of metadata with the files when I save the changes. The size of the bundle increases significantly after I make the changes.
Anyway, I figured I should let you know so that you can either update the hint with a caveat, or remove it to prevent anyone from screwing up their printer or something."
So as with most things experimental, use at your own risk!
This has been documented on other sites, but I'll post it here in hopes of saving someone else some grief. If you are installing on OS X on a Beige G3 with an Ultra-Wide SCSI card, you need to update your firmware. This is free and easy and Apple provides more information about the process. Oddly, I was able to install OS X without doing this, but I couldn't boot into it install I installed this update. The error I was getting looked like "can't open: pci/Apple53C875C".
As part of installing OS X, I upgraded my Mac from OS 8.6 to 9.1. When I first booted into it, most fonts displayed improperly and none of the icons displayed on the Desktop, making the system virtually unusable. Bad.
I eventually had the bright idea to boot 9.1 with the "base set" of extensions, without all my customizations that were there before. Then I started added back in the extensions I really cared about a few at a time to find the buggy one (I haven't found it yet-- I've been exploring OS X instead. :).
I believe to accomplish this I booted into 9.1 by holding down the shift key to disable all extensions, and then used the Extension Manager Control panel to revert the extensions to the "OS 9.1 base set". After another reboot, things looked normal.
[Editor's note: Similar tips have appeared over the last six months, but it's important enough to repeat. If your Classic environment is not behaving as expected, check the extension set. You'll want to boot with the bare minimum required to support the apps you use regularly in Classic.]
[Editor's note: Although Mac OS X includes SSH2, there is a newer version with some improvements - the most notable of which is the removal of the connection delay that you get with the current version. Here's a how-to from a macosxhints reader for the newest version. I have not tested this myself as of yet, but I'd expect it to work as described]
Installing SSH2 on OSX is relatively simple. The step-by-step I got partly from the 2.4.0 version of SSH README and in great part from http://osx.u.nu. If you'd like the full step-by-step instructions, read the rest of this article...
If you're like me, you've been terribly frustrated by the fact that "hostname name" doesn't permanently set the hostname under MacOS X. After a lot of (unsuccessful) poking around, I finally found a note on the macosx-admin group hosted by omniweb.com.
Edit /etc/hostconfig with your favorite editor. Change the line
HOSTNAME="your favorite name"
Works like a charm! Still, it bugs me that Apple has disabled many of the old unix standards - I think they'd make the platform much more attractive to a very strong unix talent base if they would try to keep the old standards where they still make sense.