Here’s Kitty!

So I’ve finally backed up my home directories and (wisely, it turned out) my Apache configuration files and installed Panther. I just did the upgrade, not the archive and install option, and I customized it just to drop most of the printer drivers and foreign languages. They take up space better spent on educational videos.

The first odd thing Kitty did was pull up my first preferred keyboard in alphabetical order (Dvorak) rather than the one I’d been using before the upgrade (US). I caught on to that pretty quick and switched back. I played with Exposé and Mail, and configured my new Finder windows. Exposé was definitely worth the upgrade. I took a short stroll through Font Book, but my main concern has been Emacs. I can’t start NaNoWriMo without my text editor. Fortunately I’m outlining my novel with the free copy of OmniOutliner, so the situation isn’t quite desperate yet. (Note that OmniOutliner has an upgrade available for Panther.)

Rumor has it that Emacs’ pty bug is gone, which I think means that ispell and other spawned processes will now work from within the GUI version. (It was an OSX bug rather than an Emacs bug, and now Kitty is all better.) It would be much nicer if Emacs actually worked.

The trouble began the first time I tried to rebuild Emacs, probably because I’d forgotten to install the developer’s tools (now called Xcode). My old build of Emacs wouldn’t run, either. I also had trouble the second time, but that looks like it was a CVS problem. I managed to get everything out of CVS and and my last build compiled, though make install didn’t move Emacs.app to the Applications folder like I expected it to. You can’t have everything, especially not at 3 a.m. Now that I look at my emacs build at a reasonable hour of the morning, I find it crashes occasionally. Such is CVS, I guess.

The other thing I did last night was redo my Apache config files, which were moved to a backup spot in the upgrade. I’m wasn’t sure what had changed so I reinstalled Entropy PHP. I’m getting a [warn] module mod_php4.c is already added, skipping, which I can’t figure out, since there’s only one AddModule statement in the conf file. I hear that may mean I have the wrong Apache build installed, but I never touched it, really, Senator. Otherwise PHP seems to work.

Maybe I should have gone with Archive and Install after all…

One Response to “Here’s Kitty!”

  1. Disco Diablo Says:

    “I‚Äôm getting a [warn] module mod_php4.c is already added, skipping, which I can‚Äôt figure out, since there‚Äôs only one AddModule statement in the conf file.”

    ——–
    This error message was also bugging me even though it was not causing any operational errors from Apache.

    If you look at the httpd.conf file where entropy is being activated, you will see that Entropy is including another config file located at /usr/local/php/httpd.conf.php whenever PersonalWebsharing is starting up.

    I got rid of the error message by:

    Open the following file in BBEdit:
    /usr/local/php/httpd.conf.php

    Commenting the following line:
    AddModule mod_php4.c

    Hope that helps, but most likely you have already fixed it by now. Just in case though, I thought I should leave a message. Ciao.

    DD