While playing around with some of the latest OS X releases tonight, I managed to mount a disk image (for an image viewer called "Outlaw", which is pretty cool, BTW, for its instant infinite scaling) which simply would not eject. When I tried, I got a message stating that the image couldn't be ejected because it was in use. I knew this wasn't the case, as I had quit Outlaw and pretty much everything else except OmniWeb. To debug and solve the problem, I opened a new terminal window and typed:
fstat | grep "Outlaw"
fstat is a file status program which identifies open files, and then the pipe (vertical bar) passes the output of fstat to grep, the UNIX search program. I asked grep to find the word "Outlaw", which was part of the disk image name. The output of the command was:
robg TruBlueEnv 804 11 19 drwxrwxrwx 264 r /Volumes/Outlaw-0.1b1
TruBlueEnv is Classic, which somehow had the image file open -- even though I had no Classic apps running! At that point, I returned to the GUI, opened System Prefs and stopped Classic. I could then eject the disk as usual from the contextual menu.
So if you've got a stuck image file, take a look at fstat with a search on part of the volume name (to shorten the returned list!) to find what's making your volume busy. NOTE: There may be easier ways to do this (UNIX wizards, any thoughts?) but this was the first one that came to mind when I was faced with the problem.
According to a tip from Macworld, if you get an error about not being able to connect to the Internet when trying to run Software Update (or Sherlock or Mac Help), you should first open a browser and point it to www.apple.com. Once you've done this, you should be able to run your update (or Sherlock or Mac Help).
Apparently it's related to an error in certain DNS servers (must include mine, as I've seen this error on occasion).
So, how many of you reboot into OS 9 just so you can empty the trash when you've got Finder Locked files in there?
How often does rm -rf fail on you with "Operation not permitted"?
You too can work around these problems with the terminal command:
chflags -R nouchg,noschg *
See the Man page for more info.
[Editor's note: I did this after doing a "cd ~/.Trash" in the terminal, to make sure I was in my trash folder. I haven't had the locked file problem, but for those that have, this could be a huge timesaver. If you'd like to see what it does first, put "echo " in front of the command.]
I've had three separate people report the same problem with Audio CD's following the 10.0.2 and iTunes update. Here's a typical story:
"I just encountered a very strange problem. I inserted an audio cd in my drive under OSX and got a dialog box that said "this disc conatins data unrecognized by OSX" and gave me 3 options...eject (default), initialize and continue.
eject is obvious.
continue makes the cd inacessable (although the tracks show up in the Audio CD player dockling, but it will not play nor eject)
initialize has virtually the same affect as continue only the songs don't appear in the dockling "
If anyone can shed light on this (somewhat widespread?) problem, I'm sure there a number of users who would be quite grateful. My machine has continued to work just fine, so I can't add any personal experience to this issue...
There have been some reports that the "Optimizing" step of the 10.0.2 update is failing for some people. It starts, but then just sits in the same spot for literally hours. A couple of different spots on the web are now reporting one possible source of trouble - an invisible file from Aladdin Systems. If your optimization fails, try this:
Boot into 9.1, and use Sherlock to find invisible files in the 9.1 System Folder that contain the word "Transaction". You may find one or two files named "Aladdin Transaction Info" or some variation on that name. If you do, delete them. Now reboot into X and try the update again; it should work fine, at least according to the reports I've seen.
My iMac would never sleep with the sleep options set in Prefs Panel. However, by simply choosing BLACK BASIC in the Screen Savers pref panel, now the iMac spins down HD after 5min and full pulsating sleep after 10min of inactivity. It seems running regular Screen savers keeps the video card busy and interferes with normal operations.. this is a G3 400DV, 320mb RAM, 10gb HD, stock.
[Editor's note: Wish I could help verify this, but I use a SCSI card, so I can't sleep the machine!]
Software Update has just given me the OS X 10.0.2 release, along with iTunes 1.1.1. I haven't had much time to use either package (it's only a lunch HOUR, unfortunately!), but here are a couple quick observations...
1) If you'd like to back up the packages before you lose them (they get deleted on restart), open a terminal and
cd /private/tmp/501 cp -R 10.0.2Update.pkg/ ~/Documents/newname cp -R iTunes.pkg/ ~/Documents/newname2
Of course, you can use any destination and name you like, and you need to do this after the packages have installed but before you select restart in the installer.
2) iTunes now has a dockling that includes "Bring to front", "Quit", "Play", "Stop", "Pause", "Next Song", and "Previous Song" (or "Open iTunes" if it's not running). It also runs visuals full screen, and (of course) includes burning!
3) From looking through the installer files (after install, run the installer package in /Library/Receipts, proceed to the "Select Destination" step, then under the File menu, pick Show Files; quit the installer when done reading) it appears that there were updates to mail.app, the login panel, audio drivers, and a whole slew of other drivers (including possbily SCSI?).
The updates are available through the Software Update panel in OS X, and as standalone downloads from Apple.
Today over at stepwise.com, they posted an article explaining a buffer overrun security hole in 'sudo', which is included with OS X. After you've read the article, you can either download an updated sudo installer, or build it yourself by doing the following in a terminal window (requires an admin account and the developer tools installed):
mkdir build-sudo cd build-sudo wget http://www.courtesan.com/sudo/dist/sudo-1.6.3p7.tar.gz gnutar -xzf sudo-1.6.3p7.tar.gz cd sudo-1.6.3p7 cp /usr/libexec/config.* ./ ./configure --with-password-timeout=0 --mandir=/usr/share/man --prefix=/usr make sudo make install
This update is highly recommended for all users, but especially those with a full-time internet connection and no firewall! ;-)
If you'd like to take some of your old System 9 alert sounds and use them in OS X, it's apparently fairly easy. I had this snipped from somewhere, and never got around to posting it. I have NOT tried this on my machine (haven't been in OS 9 lately!), so use at your own risk (but it doesn't look too dangerous).
Simply boot into OS 9.1, run the desired sound through a sound conversion program (perhaps Sound Converter Pro) to make it an AIFF format, and then drop it the into /System/Library/Sounds folder. When you reboot into OS X, the sounds should be available.
Being inherently multi-user, OS X creates a trash can for each user. There's no simple (GUI) way to empty all of these trash cans. Even if you're logged in as root, you have to remove each one individually. Over in this MacNN forum, however, 'MickS' posted a one-line terminal command that will empty all of your trash cans at once. Warning - this is not un-doable, and you won't get any 'Are you sure?' messages before the trash is emptied.
To empty all the system trash cans at once, start a terminal session and type