mac

Druplicon Mac OS X login

Druplicon on the Mac OS X Leopard login screen as the logoSwap out the Apple logo on your Mac OS X login with a Drupal Druplicon.

I followed the instructions on macosxhints.com and was able to swap my standard Apple logo on my Leopard login screen to a Druplicon. I'm sharing the GPL version of the Druplicon in the proper size and format for the replacement.

However you want to get it there, rename/replace the applelogo.tif file at

/System/Library/CoreServices/SecurityAgentPlugins/loginwindow.bundle/Contents/Resources/

with the one attached to this node or make your own 90x90 tif file.


Druplicon Mac OS X login photo

Druplicon Mac OS X login photo

Swap your Apple logo for a Druplicon.


Topics: · · ·

MySQL 5.1 on MacOS 10.5 filevault

First download MySQL 5.1 and MySQL 5.0. The GA versions are the ones that have the prefpanel for starting MySQL, so you have to get both the GA and RC if you want bleeding edge with the GUI startup.

Note: a configuration of this type is meant for a machine with one user since only that one user will be able to decrypt the filevault and unlock the data file location so MySQL can run.

Unpack the contents of 5.1.22 to /usr/local/mysql.

Mount the 5.0.45 dmg package and drag MySQL.prefPane to /Library/PreferencePanes. This is how I start MySQL. Do not click for MySQL to automatically start, because it won't be able to start until after you login your filevaulted account. MySQL does appear to be able to survive through putting a laptop to sleep, so you can just put your machine to sleep a lot if you don't like starting MySQL a lot.

Alternatively, command line nuts can start MySQL like this:

davidnorman:mysql root# /usr/local/mysql/support-files/mysql.server start

Create a place for the MySQL data files in your filevault. I picked /Users/davidnorman/mysql/data and made a global configuration file to match which I put in /etc/mysql/my.cnf. MySQL 5.0 expects the configuration at /etc/my.cnf and you will find if you use the MySQL 5.0 GUI tools, the configuration section will look there, too. I consider this a harmless penalty for using RC code.

[mysqld_safe]user = davidnormanlog-error = /Users/davidnorman/mysql/data/davidnorman.local.errbasedir = /usr/local/mysqldatadir = /Users/davidnorman/mysql/datamax_allowed_packet=64M[mysqld]user = davidnormanlog-error = /Users/davidnorman/mysql/data/davidnorman.local.errbasedir = /usr/local/mysqldatadir = /Users/davidnorman/mysql/datamax_allowed_packet=64M

Move the contents of /usr/local/mysql/data to your /Users/davidnorman/mysql/data equivalent and run /usr/local/mysql/scripts/mysql_install_db.

Start your MySQL server through Apple menu - System Preferences - MySQL. If the status doesn't turn green, check your /Users/davidnorman/mysql/data/davidnorman.local.err equivalent. My biggest problems were from permissions, which created errors that it either it couldn't find files or they were read-only. Eventually I found

$ sudo chmod -R 700 /Users/davidnorman/mysql$ sudo chown -R davidnorman:davidnorman /Users/davidnorman/mysql

cleared it up since during other parts of the install process things were created and owned by user root or _mysql and were in a few were in the wheel group.

Set a root password if you want.

$ /usr/local/mysql/bin/mysqladmin -u root password 'newpasswordhere'


Syndicate content