i'm eagerly awaiting the new update released today...but had a moment of panic. i've spent the last few months configuring (and thoroughly enjoying) apache (with many public and private sites), mysql, php, a new ftp server, etc etc...and crossing my fingers that these will still work with the update.
does anyone know if i will i have to reinstall and reconfig these? granted this would be a great test of my new skills if i did have to...
[Editor's note: Anyone installed a 10.1 upgrade over a customized system? I'm planning on installing on a newly emptied partition and then re-adding my custom pieces one at a time. From what I've read, much has changed at the deepest levels of the OS with this upgrade, and this may be the safest course of action. Any other thoughts?]
Did you ever get annoyed when you cannot see the same files in the GUI as you do in terminal. Here is a quick and easy fix to enable just those folders you would like to see. Tools such as TinkerTool let you turn on all invisibles, but this method enables each folder on a case by case basis.
Read the rest of the article for step-by-step directions.
Further to the existing posting about enabling the root user (three ways to enable the root user) Apple has posted an updated Netinfo manager method on the KnowledgeBase (you know, I much preferred the term TIL). It is Article # 106290.
[Editor: I tried to get a URL for pasting here, but the newfangled KnowledgeBase appears to be having technical difficulties. I don't know what this article discusses, but it's probably worth a read if you use your root account.]
I don't know if this has been already documented but it seems that pressing X at startup will force the Mac to start under MacOS X if the startup system folder is set to MacOS 9 (at least if your MacOS 9 system folder is on the same partition as X). I had to use this trick a couple of times because I couldn't start under MacOS 9 which always crashed during startup for an unknown reason.
Note: if you press L at startup, you won't start Linux nor Lisa (well, actually I haven't checked !) ;-)
[Editor's note: I haven't tested this on my machine, as my OS 9 partition is on a separate hard drive. I also don't know which Macs it may or may not work on, as I have not seen this documented elsewhere.]
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.
In this MacWorld forum thread, JohnKFisher asked about getting OS X version info when connecting via SSH to another OS X box. After some back and forth, PaulM contributed the easy way to get this info:
[11:13am robg ~]% sw_vers ProductName: Mac OS X ProductVersion: 10.0.4 BuildVersion: 4Q12
Just type 'sw_vers' and you'll get the info on what version of OS X you've connected to. PaulM also points out that the traditional UNIX command is 'uname -a', and that this returns Darwin information on OS X:
[11:13am robg ~]% uname -a Darwin localhost 1.3.7 Darwin Kernel Version 1.3.7: Sat Jun 9 11:12:48 PDT 2001; root:xnu/xnu-124.13.obj~1/RELEASE_PPC Power Macintosh powerpc
Many people have asked about creating bootable backup of OS X. Over in the MacFixIt forums, there was an interesting conversation about this a while ago. In this thread, "Sparky the Wonderpig" gave a fairly simple solution to the problem ... more interesting are comments from other posters concerning how it may be addressed by a future update from Apple.
If you're interested in backing up your OS X volume now, check out Sparky's method ... and let's hope we see an official tool from Apple soon!
Over on Macintouch's Mac OS X Reader Reports (well worth reading, as there's a ton of good info collected there!), Paul Christensen posted some information he received from Apple's tech support group regarding the initial setup assistant (which configures your primary user account, among other things).
According to Apple, to re-run the assistant, you need to:
Boot into single-user mode (command-S during startup)
Once the command-line prompt appears, type the following:
mount -uw / cd /private/var/db/netinfo mv local.nidb local.old rm ../.AppleSetupDone exit
When you hit RETURN after typing exit, OS X will restart and the setup assistant will launch automatically. So if you've somehow messed up your primary OS X user, this is a good fix that may get you up and running again, even if re-running the OS X installer does not.