If you haven't checked out desktopper.net you are missing out. Although the site is almost completely in Japanese, you should be able to make sense of some of the OS X GUI hacks from the pictures and scant English text.
For instance: This link points to a GUI hack to replace the "Initializing network" text at startup with whatever you want.
Navigate to '/System/Library/StartupItems/Network/Resources/English.lproj' with the Terminal (substitute the other languages for 'English' if necessary). Now type 'pico Localizable.strings'. Replace 'Initializing network' between the String tags with whatever text you want.
You will need a restart to see this one, a logout doesn't show this window.
The official OS X 10.0.1 update is now available from the Software Update control panel. It will first update Software Update, then you need to launch Software Update again, and it will download the 10.0.1 updater (about 4mb in size). The "About This Mac" box now reads "Version 10.0.1 (Build 4L13).
The updater will put a "Late Breaking News" item in your dock, but it contains no update-specific information (ie there's nothing that says exactly what was changed). The only information I've seen about the update is on Apple's web site, where they claim:
Improvements include better support for third party USB devices, Classic compatibility and overall application stability as well as support for the popular Secure Shell service. For Japanese users, an update to the Epson printer drivers is also available.
Either later tonight or tomorrow morning, I'll be updating my benchmarks with post-update numbers for comparison purposes. If you have further information, questions, or comments on the update, post them here!
This may seem obvious, but I forgot to do it one so I figured I would warn everyone else...
If for some reason you do a fresh install of OS 9.1 (including from the CD that came with OS X) remeber to run the software update control panel to update the OS before switching over to OS X. I forgot to do this and Startup Disk TOASTED my OS 9.1! I was able to re-install it, then quickly ran software update to fix the problem. Aparently the version of startup disk included on the OS 9.1 CD is not compatible with OS X.
Re-run for man2 to man8... Also run on any other man directories you might have (like /usr/X11R6/man if you installed XFree86 or /usr/local/man if you installed lots of 3rd party UNIX software).
The command will compress the man pages, significantly reducing their space usage. after that, 'man' will be a bit slower because it has to decompress all the man pages before display, but it's worth it if you want some drive space back.
Many users of dual G4's who connect to the internet via the internal modem and PPP have been reporting repeatable kernel panics. In the "great news!" category, Darwin Developer Louis Gerbarg has created a modified Apple Serial driver that appears to have resolved the kernel panics!
You can read the thread about the original driver's problems and the solution on this MacNN Forum thread, and you can download the new driver here:
We know that the contrast keys on PowerBooks work if you have the Display preferences panel open. Apparently, this is because of a process called DisplayServices, which is located in System/Library/Displays.
If you have this app run everytime you log in (by dropping it into the login preferences panel) then your contrast keys should work. This worked for me, albeit with approximately 1 minute of testing.
If you're looking for a way to move your installed OS X to a new volume, Robert Hancock posted a new method in this Macintouch Reader Report.
Supposedly, if you download Apple's Software Restore program (note: I can't find it on Apple's servers, but there's one on my 9.1 volume), you can boot into OS 9.1, run Software Restore, and tell it to restore your OS X partition or drive to your new drive. This will handle all hidden files and folders. Sounds like a fast, simple way to move a complete OS X installation to a new drive.
NOTE: If anyone can help with this, it'd be appreciated. I found Apple Software Restore, but when launched, it simply says "Cannot find any configurations to restore" and quits. Robert claims to have used this method a number of times, but I can't make the program do anything other than launch and quit.
If any of you have had problems with OS X crashing a lot (perhaps even during installation) on PowerBook Lombards, you are not alone. Lots of people have had this problem. It appears to be caused by the presence of RAM modules beyond the base 64MB. If you have a RAM upgrade in your top slot, OS X should work fine after you remove it.
It is unclear what is causing this problem, at first people said it was due to tighter memory tolerances, but then reports came in about even apple RAM upgrades causing the crash. Now it seems like it may be a lingering hardware bug that wasn't revealed by previous OS's. You can read lots more about this on the MacFixIt Forums in this thread.
Apple does not have a fix for this yet, in fact they appear to be denying that it is a problem, so I encourage anyone else experiencing this bug to fill out a bug report form.
Scott Anguish of Stepwise has written a very good article that discusses some serious problems with Apple's package installer program. It's a bit technical at times, but a couple of key tidbits include:
If a package installer encounters a directory that already exists, it will set its permissions and ownership to the permissions of the version in the archive. If the installer maker wasn't very careful with the permissions settings, you may find your Applications folder has new permissions which make it impossible to use (jCalendar originally shipped with such a problem, and the author has now switched to a disk image installer as a result)
If you have a symbolic link that points to another directory (if you've moved your Applications directory, for example, and replaced it with a link to the new location), the installer will replace the link with a directory, and any files below that directory will be installed in place. This can also have serious side effects, including disabling your system completely.
If the installer package requires your password to launch, then code inside the package that's owned by root will be executed with full root privileges. This makes it very easy for malicious code to damage areas of your system which would normally be protected.
In short, until Apple resolves the problems with the installer maker, you should treat any .pkg file with extreme caution - it could easily disable key portions of your system, and it would be fairly trivial for a malicious hacker to create an installer that does a number of Very Bad Things using root privileges.
This is a tricky situation, as some products (such as mySQL and PHP) seem to require an installer, based on their need to put pieces in a number of locations. In general, avoid the package installers if you can, but if you can't, make sure you (a) have a backup of important data before proceeding, and (b) know and trust the source of the package.