While working on an iMovie project tonight, I noticed something about the (much much loved!) ability to render transitions and other effects in the background. I started a large number of transitions rendering (probably 10 or so), and then switched back to the Finder. The machine (a G4/733) was usable, but very very jerky. I saw the spinning rainbow occasionally, and switching apps and selecting menus was very slow.
In the interest of trying anything to see if I could regain some speed, I hid the iMovie application. Amazingly enough, this made a huge difference. Although I can still tell there's background work going on (the CPU meter is pegged, for example), I have full control over the machine, the windows don't lag, and I haven't seen the spinning rainbow since hiding iMovie.
This is a very small sample size (one machine!), so I hate to jump to conclusions, but I've repeated the experiment a number of times with the same results. If iMovie is visible in the background while rendering, the machine slows dramatically. If iMovie is hidden while rendering, it's hard to tell there's much out of the usual going on.
If you work in iMovie, give it a shot and let me know if you see similar results...I'm intrigued!
The terminal's font spacing (even for monospaced fonts) suddenly went wacky and I haven't had any luck getting things back to normal.
Typed entries at the command line and even in editors like vi are offset by half a character to the right (relative to a normally positioned text, as output by "ls" for example). Pressing backspace returns the remaining characters to the "correct" position.
After deleting the terminal preferences, things go back to normal until the font size is changed from the default size.
Has anyone seen the following problem? If so is there a recommended remedy?
In the midst of looking for something else, I stumbled across an 'older' (May 2001) article concerning power management with OS X on PowerBooks. In the text of the article, there's a fairly good example of how to use "ps" and "grep" and a couple of other UNIX commands to get a handle on what may be going on with your system if you're experiencing slowdowns or fast-draining batteries.
If you're interested, head over to O'Reilly's web site and read Mac OS X and Battery Life by Derrick Story. Although Derrick wrote the story, the majority of the content is from a note submitted by Peter Fraterdeus, a long-time Mac user and developer. Peter gives some very good examples of how to use the features of the core UNIX system to identify potential trouble spots. Most of the article is relevant not just to PowerBooks, but to Mac OS X users in general.
If you're wondering why OmniWeb 4.0.X displays Arial instead of Verdana when Verdana is selected as the proportional font (very annoying and ugly IMO), I've been told by tech support at OmniGroup that there is a problem with the font metrics for Verdana under Cocoa and they are waiting for Apple to fix it before they re-enable Verdana in OmniWeb.
(Can anyone suggest a good non-serif replacement for Verdana until this is sorted out. I can't live with Arial or Helvetica so I've gone back to Geneva for the moment.)
Since reading a recent Hint, I'm compiling a C++ scientific computing package to run on OSX and do some parallel calculations on my dual G4 (MPI and OpenMP). It's all working fine except when I turn on a feature that uses the functions drand48() and sdrand48(), which are a random number generator and a seed respectively. In OSX they aren't defined.
On other *nix systems these functions are defined in stdlib.h, and the corresponding library. Taking into account that I have never compiled a library without explicit instructions - is there an easy way to add these functions without doing anything dangerous to the libraries that came with OSX? Could I replace the standard library safely?
I've currently installed bash and rpm if that would shorten the instruction list at all. Thanks for any help,
i think i saw a link here about this--cant remember [Editor: I thought I remembered it, too, but can't find it anywhere!]. anyways, here's a really cool UNIX admin application i just downloaded. go to: The Moose's Apprentice page and check it out.
i haven't had time to "battle test" it yet, but the documentation is *excellent.* I'll use it tonight to restrict ftp users to their home directories...an app like this is precisely what ive been looking for. hope it lives up to its potential.
[Editor's note: Based on a quick five-minute look, this looks like a very impressive application. It gives you a GUI tool to manage many of the low-level UNIX tasks, such as cron jobs, FTP user access, allowed shells, and authorizing services by user and address. Worth a look-see if you're looking for a way of handling some of the UNIX stuff without diving into the terminal. A note of caution, though - this app will let you change things that you may not fully understand! Make sure you have some concept of what you're changing before you start tweaking the settings...]
I would have never really pushed to get this to work, but I needed to have xwindow working for a class that I am taking... After all the work I put in I figured I would give a few pointers that took many hours to figure out (mostly because of my unix ignorance). First of all download the files from xfree86 download. I put all the files into a folder called xfree86 and stashed it onto my harddrive. I then fired up the terminal and got to the xfree86 directory. Next I entered
sudo perl Xinstall.sh
I tried it the first 2 times with out sudo and it did not work very well. After this runs go to and download the newer XDarwin. This runs rootless (this means that OS X is still visible in the back ground). It takes a little while for the whole thing to load, but it seems to work. Granted I do not know much about this whole thing... but it may be nice to know if you are like me, that using Sudo makes the install actually work!
I recently bought a new hard drive, and wanted to install another copy of OS X on it. I figured I would just take my "Classic OS 9" and copy it from my current drive to the new drive. I did this while booted in OS X, and it copied over just fine. When I went to the "Classic" system prefs panel, however, I could not select the OS 9 I had just created - the volume was greyed out, as though there were no allowable system on that drive.
I could have rebooted into OS 9 on that disk and then back into OS X, but that seemed like too much work. Instead, I switched to the Startup Disk prefs panel. When I did that, the panel started the drive scan it always does to find bootable volumes ... and it noticed my new OS 9 folder on the new drive, and listed it as an avaialble startup disk.
I then went back to the Classic panel and was able to pick that same OS 9 as my Classic volume. Somehow running the Startup Disk panel 'blessed' the new OS folder I had copied, saving me a couple of restarts.
The following will search the current dir (and subdirs) for any files that contain identical content and are of identical size, regardless if they are named differently. Open a terminal shell, and 'cd' to the dir you want to search, then type:
[Editor's note: I inserted a carriage return for readability -- type the command on one line when entering it!]
This will produce a list of duplicate files (if any) in dup.txt. True there are some nicely written apps that will do the same thing, but ain't it great that you can do this right from within your OS?
This will ignore files that are smaller than 10k. (remove/alter the '+size 20' to change this). But a warning: really small files may produced identical CRCs. i.e. show up as duplicates even if they really aren't.
If you want to search a filesystem you don't own (i.e. /) you'll need to sudo or su or 'find' will complain.
The built-in cksum cmd only uses CRC32. MD5 would be better. Anyone know why it's not enabled under OSX?
If you're gonna write a script to delete the duplicates from the produced dup.txt list, just remember that it contains ALL instances of the duplicate files.