ewx: (marvin)
chymax$ ls -lL /usr/X11/lib/libXdamage.*
-rwxr-xr-x 1 root wheel 88496 2009-03-13 00:38 /usr/X11/lib/libXdamage.1.1.0.dylib
-rwxr-xr-x 1 root wheel 88496 2009-03-13 00:38 /usr/X11/lib/libXdamage.1.dylib
-rwxr-xr-x 1 root wheel 88496 2009-03-13 00:38 /usr/X11/lib/libXdamage.dylib
-rwxr-xr-x 1 root wheel   936 2007-09-24 05:39 /usr/X11/lib/libXdamage.la
chymax$ grep ^library_names /usr/X11/lib/libXdamage.la
library_names='libXdamage.1.dylib libXdamage.dylib libXdamage.1.0.0.dylib'
ewx: (geek)
Further to the instructions here, I'd add that you will need to randomly re-install the new layout from time to time, as Windows randomly breaks or removes it without even telling you.
ewx: (geek)

I used to have /usr/local be a symlink to /local, but after a recent update:

$ find /usr/local | xargs ls -ld
drwxr-xr-x 3 root wheel   102 2009-03-20 09:26 /usr/local
drwxr-xr-x 3 root wheel   102 2009-03-20 09:26 /usr/local/bin
-r-xr-xr-x 1 root wheel 43312 2009-03-10 22:30 /usr/local/bin/iTunesASUHelper
ewx: (geek)

This image raises two issues:

  1. Why does the Mac disk get an anti-aliased font and the Windows one a pixelated one?
  2. Just how many fonts does a boot loader actually need?
ewx: (Default)

A while ago I wrote that Spaces was rather a disaster. I'm pleased to say that in the latest version of Leopard, 10.5.3, it's considerably improved. The key is the ability to turn off this option:

I no longer find myself being dragged from space to space at the whim of the window manager. X11 integration seems ropier, but it's not exactly perfect even with a single desktop anyway, and having installed Aquamacs I'm no longer reliant on X11 for one of my most-used applications.

ewx: (geek)

I've enabled Time Machine. It took a few hours to back up 70GB or so to an external disk. It didn't back up the Windows XP partition; I'm not sure I approve but considering that as a separate machine and therefore organizing backups of some form separately is not something that actually bothers me that much.

Not much more to say about it at this point; it's rather in the nature of backups that you don't just enable them and know all you need to know...

ewx: (geek)
=== modified file 'scripts/setup.in'
--- scripts/setup.in    2008-01-19 12:28:31 +0000
+++ scripts/setup.in    2008-03-29 15:24:01 +0000
@@ -220,32 +220,32 @@
 case $os in
 Mac )
   # Apple don't seem to believe in creating a user as a discrete operation
-  if dscl / -read /Groups/$group >/dev/null 2>&1; then
+  if dscl . -read /Groups/$group >/dev/null 2>&1; then
     echo "$group group already exists"
     echo "Creating $group group"
-    gids=$(dscl / -list /Groups PrimaryGroupID|awk '{print $2}')
+    gids=$(dscl . -list /Groups PrimaryGroupID|awk '{print $2}')
     gid=$(pick $gids)
     echo "(picked gid $gid)"

(etc etc). Amusingly this means their own example is now broken.

Last batch of ranting about Apple's hopeless approach to user creation.

Boot Camp

Mar. 15th, 2008 02:51 pm
ewx: (Default)

Further to my remarks on Leopard one of the reasons for buying it was to add a Windows partition to my Mac via Boot Camp.

Boot Camp comprises a partitioning tool, support for dual boot and a collection of drivers (on the Leopard install disk) for running Windows on Apple hardware. You need an Intel Mac and a sufficiently recent copy of XP or Vista. In this version only 32-bit software is supported even though I have a 64-bit CPU, but I hear that more recent Macs are shipping with 64-bit capable Boot Camp. 64-bit operation isn't particularly important for what I current want out of Windows anyway (games and the odd bit of software development).

Partitioning was perfectly easy. On booting into the Windows XP installer the keyboard didn't work initially; after I unplugged my USB card reader and rebooted it was OK, however. I'm not sure if this is Apple's bug or Microsoft's but it seems to be a common problem.

The network setup decided to apply the address I gave it to the firewire port rather than either of the ethernet ports. I disabled the firewire port (under windows) and the non-connected ethernet and it was happier. (As with my Windows/Linux dual-boot system) I'd given the Windows partition a different name and address to the MacOS partition.

SHIFT 3 on my UK keyboard produces £, which is not what I wanted; I type # much more often than £. Under Mac OS I was able to select a US keyboard layout but Windows doesn't offer me a US Apple layout (and the US layouts it does have have other keys in the wrong places).

Here's what I did to get around this:

  1. Install the keyboard layout creator from http://www.microsoft.com/globaldev/tools/msklc.mspx and run it
  2. Load the Apple UK layout
  3. Change £ to # and vica versa, using CTRL+ALT+3 to type #
  4. Select Project->Properties and edit the name etc
  5. Select Project->Test Keyboard Layout to make sure it works
  6. Save the source file
  7. Selected Project->Build DLL and Setup Package
  8. Quit the layout creator
  9. Install the new layout package
  10. Go to Control Panel->Regional And Language Options->Languages and make the new keyboard layout the default

Rather surpringly the choice of keyboard layout doesn't seem to be reachable via Control Panel->Keyboard.

I installed the following things without any difficulty:

  • PuTTY
  • Firefox
  • Windows updates (needed 2 restarts)
  • IE7
  • Starcraft and Brood War
  • Rome: Total War
  • Warcraft III
  • Visual C++ 2008
  • RealVNC
  • DirectX SDK (March 2008)

Half Life said it didn't like my OS (it predates XP by some years) and needed a patch, but after rather fruitlessly poking around the web for the right thing (which used to be on Sierra's website but isn't any more) I installed Opposing Force and it installed a patch and ran OK anyway.


Mar. 10th, 2008 10:18 pm
ewx: (geek)

The installation process was smooth enough. I had to restore my user icon but I didn't notice anything else going missing. I had to upgrade SSHKeyChain but it needed upgrading anyway it turns out Leopard can manage without.

First Impressions: mostly good, but Spaces is awful )

I'll be giving Boot Camp a go in a bit.

ewx: (geek)
--- server/play.c       2008-03-03 22:56:22 +0000
+++ server/play.c       2008-03-09 11:10:46 +0000
@@ -389,8 +390,14 @@
       /* np will be the pipe to disorder-normalize */
       if(socketpair(PF_UNIX, SOCK_STREAM, 0, np) < 0)
         fatal(errno, "error calling socketpair");
+      /* Beware of the Leopard!  On OS X 10.5.x, the order of the shutdown
+       * calls here DOES MATTER.  If you do the SHUT_WR first then the SHUT_RD
+       * fails iwth "Socket is not connected".  I think this is a bug but
+       * provided implementors either don't care about the order or all agree
+       * about the order, choosing the reliable order is an adequate
+       * workaround.  */
+      xshutdown(np[1], SHUT_RD);       /* decoder writes to np[1] */
       xshutdown(np[0], SHUT_WR);       /* normalize reads from np[0] */
-      xshutdown(np[1], SHUT_RD);       /* decoder writes to np[1] */
       /* Start disorder-normalize */

August 2017

13 141516171819


RSS Atom

Most Popular Tags

Expand Cut Tags

No cut tags