[Editor's note: See the comments for a good discussion and solution to this question]
I just managed to get bash compiled and running but I have a problem whenever I switch the shell in Terminal.app's preferences.
If I set it to bash, zsh or anything besides tcsh, it seems that I can only use commands from /bin. I mean, I'm missing basic stuff like ping and traceroute. I can su root and copy commands from /sbin or /usr/bin, but this doesn't seem like the right way to go about using my spiffy new shell.
Oddly enough, I can start Terminal with tcsh and then temporarily switch to bash, and everything works perfectly. Tried using chsh, but it launches vi, and vi and I are not on speaking terms.
Need help from someone who knows what the heck I'm doing wrong.
Whew! Just got through installing DNSUpdate. I had trouble with the installer. It started up, but didn't seem to do anything. By looking at the uninstall directions, I figured out how to install it manually though.
I untarred the Files.tar.gz in the installer:
sudo tar xzvf DNSUpdateInstaller.app/Contents/Resources/Files.tar.gz
That got me most of the way. But it seems that the location of the StartupItems folder has changed since the Public Beta, so I had to move it:
[Editor's note: I have replaced the original method listed here with a much safer version. The "find" command line hack removes some Epson and Apple files that also end in ".lproj".]
If you plan on using your machine for only English (or only one of the other languages), you can safely remove the foreign language files (*.lproj) from your drive, freeing up over 200mb of space. "Since EBCDIC" posted a script in this MacFixit forum thread that does the trick.
maybe one can try to alter the script for other apps, compile 'em and then, using script runner, windowshade'll be back. :) i know, i'm dreaming...
[Editor's note: Marcus, I don't think you're dreaming. If they left the capability in the system, then I believe someone will be able to write a windowshade application, if nothing else. That would make some people very happy! To test these scripts, copy/paste them into the ScriptEditor application in the AppleScript folder]
Update: The above-referenced Apple page no longer exists. However, using the Wayback Machine, I was able to find the original scripts; they're now listed in the rest of this article...
[Editor's note: See the comment for the answer to identifying the installed files]
I took the lazy route: used a clean partition for the OS X install but used my 'everyday' System 9.1 on the other of the two partitions for the Classic environment. Now I'm rethinking this strategy, or lack thereof, and I'd like to put a minimal OS 9.1 on the same partition as OS X for the purposes of running in Classic mode. No problem there, but I'd also like to clean out my 'everyday' 9.1 of OS X files and extensions: Is there a list of these files and their locations somewhere?
[Editor's note: See the comments for a discussion and potential solutions to this problem]
I just redid my hard drive configuration on my PowerBook g4. I now have 3 partitions. 1 for OSx - formatted usi ng the UNIX file system, 1 for os 9.1 formatted in HFS+ and a big partition i use for storage which is formatted also using HFS+. I'm in osX and every time i try to start up classic i get a very interesting error message saying:
"This startup disk will not work on this Macintosh model. Use the latest Installer to update this disk for this model." ... and it gives me only one option to click on: restart
What does this mean and how can I fix it.....
When you use a filename that's too long for the Finder to display, OS X replaces the middle portion of the name with "...". You can make the full name show up by hovering over the name for a second, or editing the filename with a click and mouse movement.
A much much quicker method is to simply browse the file list wth the option key held down. Every filename will instantly expand as you mouse over it's position in the list. Cool!
I read this on one of the 10,000 different web pages I visited this weekend ... sorry I can't remember the source!
I would just like to say that you don't need to remove any files to get soundsticks to work, as was required in the beta. I plugged mine into my Cube 450 and they didn't work at first, but after I downloaded iTunes I noticed they worked, just not loud enough (system was set at max volume) ... so I lowered the volume, and the actual volume jumped up. Apparently, X does work with soundsticks, just not right away.
I got X on my system on the 24th, and now it's two days later and I haven't restarted yet!
I've purchased and installed Mac OS X on my Blue & White G3. Now I'm looking for ssh. Is it missing from this release? It was present in the Public Beta and I need secure telnet to be able to work from home.
Typing 'ssh' in a terminal session results in the shell trying to resolve my unknown command to 'sh' instead.
I have installed everything available on both the Mac OS X Installation CD and the Developer Tools CD. Any help would be greatly appreciated.
Steven M. Fish
[Editor's Note: See the comments for a couple of methods for installing SSH. The URL for the Stepwise how-to is: