It's been noted here and elsewhere that X11 in Leopard is different from Tiger. You don't have to (and in fact, shouldn't) launch X11 explicitly in Leopard. Just do an ssh -Y hostname to a remote machine in Terminal, and when you launch a remote X app, X11 automatically starts in Leopard. You'll see it in the Dock. What's not obvious is something that happened to me today:
I upgraded my home Mac from Tiger to Leopard, and everything went fine. It was with the "fresh" Archive and Install on my laptop where I had issues with X11. Basically, everything seemed normal, except X11 apps would not launch. Long story short, it was the Archive and Install from Tiger to Leopard that was the problem!
A clean install of Leopard will not install X11. However, if you're coming from Tiger and already had X, the old X11 app is not removed from your disk! So you'll see the presence of X11 in your Applications folder and be fooled into thinking you still have X11 installed. And in fact, it will start up in the Dock the way X11 is supposed to in Leopard when it's called from a Terminal command that needs it. It just won't actually work -- very confusing.
The solution is to insert your Leopard DVD (no need to boot from it) and install 10.5 X11 from the Optional Installs installer. Then everything will be fine. Or just do an Upgrade install at the outset and have no problems!
The file OSInstall.mpkg is the key to Leopard installs from a disk image. There is no need either to use the DVD again, or to reboot, to install Leopard to a different volume. After installing any Mac OS once from DVD, I always use Disk Utility to save the installer DVD as a disk image. Any further installs are from copies of this disk image; I put the original DVD away never to touch it again. I keep many external bootable drives, so the fire never goes out, so to speak.
On OS X install disks, it has always been the case (and remains the case with Leopard) that the top-level Install Mac OS X icon wants to reboot, but buried in the disk is a file named OSInstall.mpkg that can install OS X to a different volume without rebooting.
Reports that this is no longer possible with Leopard are in error. What has changed is that the folder structure is now hidden to the Finder. The needed path is still visible in Terminal, and one can use open in Terminal to reveal folders in the Finder. I then save an alias to OSInstall.mpkg next to each copy of the disk image (Command-Option-drag). Whenever I want to install OS X, I mount the disk image, click on the OSInstall.mpkg alias, and we're off to the races.
The Terminal command to open the enclosing folder for OSInstall.mpkg on a mounted Leopard install disk image is:
open "/Volumes/Mac OS X Install DVD/System/Installation/Packages/"
This was widely known and was easily discovered by poking around for previous versions of OS X; a search here for OSInstall.mpkg reveals many posts about this. What's new in Leopard is that the folder structure is now hidden.
This really old hint has the basics for resetting a machine back to no users, so it boots to the Setup Assistant again. Things have changed in Leopard, so here's some new info.
This hint will probably be most useful for folks who configure machines for a living, but if you're selling or giving away your machine, or just troubleshooting login issues, it may come in handy. Here are the Terminal commands to delete a temporary (or lone) account in single-user mode on Leopard (in the following commands, replace username with whatever account short name you've created). Note that this must all be done in single user mode (hold Command-S during boot).
I thought I'd share the details of how I successfully managed a "non-standard" installation of Boot Camp in 10.5. Basically, I wanted three partitions on my startup drive: System, Users and Windows. (I don't want a debate on the merits of partitioning; it works for me, and the one time I didn't do it, I lost a ton of stuff due to 10.1 weirdness).
So, Boot Camp Assistant will not allow this. Full credit for the workaround goes to AxL over at Apple Discussions. I just tweaked the original a bit, and included some additional details. Read on...
If you are like me, you have several Macs about the house, both old and new. I was a little disappointed that my old G4 800 tower did not meet the install requirements for Leopard.
However, there is a workaround. I installed Leopard on a machine that met the requirements to a FireWire drive. When the install finished, I shut down the installer machine and put the drive back in the 800MHz G4. Voila, it booted right up and finished the setup; it worked like a charm. Leopard also seems to run faster than Tiger did. So I will get a little more life out of the old beast still.
I just installed Leopard (os x 10.5) and as most other users are very happy with it. Until I ran into this little problem: Lotus Notes 7.0.2 will not install. The install script gives an error and forces the install to quit. However I was able to find the problem and force the system to give the correct information to the install script. Here is what I did.
The problem is that the installer for Lotus Notes runs a shell script that determines a few things about your computer, amongst them the current OS version. If the version is not 8 (nothing lower, but also nothing higher) the installer will quit. It uses the sysctl to determine the version. What I did was rename sysctl to something else and create a shell script in the place of sysctl (/usr/sbin/) that only returns what the installer wants to hear.
[robg adds: What follows is potentially very dangerous, as it modifies a key system file. Read on for the details, but be aware that I don't think this is perhaps the best solution (nor do some of the commenters on the queue review team). However, it worked for the submitter, and may help someone else, so read on if you need this information.]
Apple usually weeds out a few machines with new versions of OS X, but 10.5 is the first release I'm aware of that will exclude a larger number of machines from being able to run the new OS. For example, my trusty G4 fails to meet the minimum processor requirements -- it has enough RAM to run 10.5, but the installer prevents me from installing. I doubt I'll be alone here.
All is not lost, however, as it is possible to modify the file that checks the machine specs and decides if 10.5 can be installed.
We first need to restore the 10.5 DVD onto a read/write media. I typically use an external FireWire drive for this. It is as simple as attaching the drive and inserting the DVD into the machine. Then launch Disk Utility and select the drive/partition to restore the DVD onto. Drag the DVD to the source area and the drive/partition to the destination area, and start the restore.
If this was 10.4, we could simply edit the Distribution file in the mpkg file, but Apple has changed things -- they now use xar to compress the mpkg file, so we'll need to decompress the mpkg file and then edit the Distribution file.
I own an old CRT monitor that I use with my Mac, and it's default display resolution is 640x480. This is fine, as I have it set to 1158x864 and things work.
But when popping in the Install CD, I could not even hit the Continue button to start installing. With no drivers or preferences, the old monitor defaulted to a resolution no longer supported. When I called tech support, their solution was buy/borrow a newer monitor.
So instead, I partioned a drive to 7.8 GB (a little extra space), and restored OS X 10.5 from the install disc. Then I copied over the com.apple.windowserver.plist file from my working /System/Library to /System/Library on the new partition. You may need to manually open that folder in either the Finder's open dialog or via the open command in the Terminal.
I then ran the installer from that partition, and everything worked. Hopefully this was helpful.
If your Mac is bound to Active Directory (AD), make sure you unbind it before upgrading. Also make sure you have a local admin account (that was not created via AD) beforehand. I had a tough time with a Mac here -- the only account on the machine was created through authenticating via AD. In case this happens to someone else, and they find this, here's a fix:
Start up in single user mode (power on while holding Command-S) and enable the root account by giving it a password (by typing passwd and entering a password). Then reboot and log in as root. Once you've logged in (it was very slow for me), go into Directory Utility (/Applications » Utilities) and you will see the AD entry listed there.
For me it showed as connected, but was not getting the proper info. Unbind it, and as soon as it's done, you should see an immediate improvement. I was not able to log into my old account; I had to create a new (local) one, and then transfer the old home folder to my new one. I think I added that hint before, but here it is again, in case I didn't: