The bit that says up 8 days 15 hours is what I am interested in. Reasons for rebooting would also be of use. For example I have found that over time my idle process time goes down so drastically that I must periodically reboot to improve overall system responsiveness and stability. But I also tend to get a kernel panic every 5-8 days as well. Others may find that they have to reboot into OS 9.x to use some app. 8.5 days is the longest I have been able to remain up thus far. I look forward to hearing about this...
[Editor's note: Seems like a reasonably interesting topic, given the relative lack of OS X news lately! Chime in ... my current uptime is 2 days, 23:15. Last reboot was due to a need to burn an iDVD.]
Lots of people have been complaining or commenting on how there is no way to use the 'tar' command to backup, share, archive, copy, etc. files on the Mac that have resources and desktop information. Well after a few days of trial and error I have found a way.
I call it "tarw" - The tar Wrapper.
tarw is essentailly a perl script that uses the tar command to archive files individually. This allows you to archive resource forks, desktop files any data that you can get your hands on essentially. The current version simply ads support for resource forks and desktop information like creator, type and attributes. In the future who knows what is possible.
I have placed a gzipped file "tarw.tgz" on my iDisk you are free to download at:
To use the program, simply download and extract it. There is a readme file included with it.
Please provide feedback to this posting or if you like e-mail me I would love to hear what people have to say about it.
Good Luck and long live the Mac.
[Editor's note: I haven't tried this myself yet, but it sounds like a handy command-line utility!]
Just a quick note to let you know: I have a Logitech USB optical 2-Button Wheelmouse (3-button if you include the wheel!). It used to freeze if left unused for more than about 15-20 minutes. Pointer would not move, but mouse seemed to be registering the movement (optical LED lights up).
With update 4, I have not had a freeze in 4 days. Seems they fixed some USB issues - Yipee!!
By default, Apple's mail.app will mark a message as 'read' as soon as you click on it. There's no preference setting to prevent this from happening, but a member of the Apple mail team gave one workaround on the X4U mailing list.
Simply move the "preview" horizontal divider (the line that separates the incoming mail list from the message body) all the way to the bottom of the screen. The easiest way to do this is to double-click the line itself. This causes the Preview panel to vanish, and messages will no longer be marked read as soon as you click on them.
Symptom: Print Center says your document is printing, but nothing is happening.
If you have a printer supported by X that prints sometimes but not at others, it may be that you have too many applications open, thus preventing Print Center from getting the RAM it needs. I've discovered that X (any build) doesn't provide an error message saying "there is not enough memory for this task" (or some such).
Like many others, I've gotten in the habit of leaving my frequently-used apps open all the time, and with 617 Mgs of RAM, I thought I had plenty of memory to spare.
But on trying to print some docs, the Print Center would open and say the doc was printing (no error message) when in fact nothing was happening. When I tested with a one-word doc ("testing") it would print fine.
I quit several other apps, and now my more complicated doc printed just fine.
So if suddenly your printer is unresponsive, try again with fewer applications open in the background!
A reader is looking for information on some advanced FTP server options in OS X. He's tried the various boards and had no luck, so I'm posting here in case there are any answers out there. He writes:
I've looked near and far and have heard from many other people the same problem. Finding a concise document to set up a FTP server on OS X is hard to find. Basically I am looking for some tips on these few tasks which I can not figure out and I believe would help many other OS X newbies:
I have set up a ftpchroot file to resrict users to their home directories, but how do I provide them a link in their home directory to a community folder for all of them to upload and download from?
How do I limit access to say two logins per user, and limit their bandwidth?
How do I go about setting up groups in user administration say so that all FTP users would be in thier own user group of FTP?
If anyone could shed some light on these relatively simple tasks which are complicated to us newbies please please feel free to provide some answers. Thank you.
If you command click an item in the dock, it reveals that item. But I noticed that this also works if you are inside a folder's popup menu in the dock and command release on an item. It will reveal that menu item in the Finder.
I have seen some scattered reports of problems connecting to other systems using 10.0.4 (which includes OpenSSH 2.9p1, according to Apple's documentation). The connection begins, but then terminates with the message "Disconnecting: Bad packet length -898731090", or just fails to connect. To help debug the problem, you can try using SSH with a -v option, which is verbose mode and will show you the details of the connection attempt.
The X4U mailing lists have had some discussion on this topic, and have come up with three possible solutions:
Try connecting with the 'blowfish' encryption scheme (ssh -c blowfish xxx.xxx.xxx.xxx)
Compile and install OpenSSH 2.9p2 on your OS X box (there are instructions on StepWise)
Upgrade the other machine (if you can) to OpenSSH 2.9p1 or later
Try forcing SSH to use SSH1 instead of SSH2 (ssh -1 machine.domain.com) [noticed on MacFixit this morning]
Regenerate your SSH keys (use ssh-keygen at the command line) [from the comments below]
Each of the above methods has worked for at least one user. Personally, SSH is working for me just as it did before the upgrade, but if you're having troubles, try one of the above solutions.
Check your Software Update panel - it's out there! This is from the Read Me:
"The 10.0.4 Update delivers a significant number of improvements for USB devices including additional external device support for iTunes CD burning, improved battery life for many PowerBook G3 systems, and Classic compatibility improvements. This update also provides the latest security updates to OpenSSH and 'sudo' services and includes support for Apple's newest digital flat-panel, the 17-inch Apple Studio Display."
The list of modified files is way too long to post here -- you can see it yourself by doing this from the terminal:
[prompt] cd /Library/Receipts/10.0.4Update.pkg/Contents/Resources [prompt] lsbom 10.0.4Update.bom
Don't type the [prompt], that's just my representation of your command-line prompt. This will show you all the updated files installed by the updater.
NOTE: Apple has released (for the first time!) update notes which detail exactly what was changed, in easy-to-understand language. Give them a read-through to see everything that was updated (and why!).
Back in the OS X Public Beta days, Ryan Rempel created a hack to get OS X installed on older machines. Now, thanks to Other World Computing, he's been able to create an installer that handles a number of the older machines with the release version of OS X. Read all about it (and download the installer) on Other World Computing's OS X for Legacy Macs page.