gregs » mac

Recursive delete

gregs — Mon, 22 Mar 2010 05:30:52 +0000

I new it was possible, just never took the time to look it up.

PLAIN TEXT

CODE:

rm -rf `find . -type d -name .svn`

As with all types of deletes, recursive or not, use with caution.

gnumake: *** No rule to make target `all’

gregs — Tue, 07 Apr 2009 01:29:58 +0000

I was using MacPorts to install ICU and Jam. After running the installer for the first time I got the following error message:

PLAIN TEXT

CODE:

sudo port install icu jam
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_icu/work/icu/source" && gnumake all " returned error 127
Command output: sh: gnumake: command not found

Oops forgot to install XCode (you always forget to install something on a new machine ). Quickly ran the XCode installer, however when I ran the command again I got a new error:

PLAIN TEXT

CODE:

sudo port install icu jam
---> Building icu
Error: Target org.macports.build returned: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_icu/work/icu/source" && gnumake all " returned error 2
Command output: gnumake: *** No rule to make target `all'. Stop.

Turns out you need to do a cleanup before attempting to run the command again:

PLAIN TEXT

CODE:

sudo port clean --work icu
---> Cleaning icu
sudo port clean --work jam
---> Cleaning jam
sudo port install icu jam
---> Fetching icu
---> Verifying checksum(s) for icu
---> Extracting icu
---> Configuring icu
---> Building icu
---> Staging icu into destroot
---> Installing icu @4.0_0
---> Activating icu @4.0_0
---> Cleaning icu
---> Fetching jam
---> Attempting to fetch jam-2.5.tar from http://distfiles.macports.org/jam/2.5
---> Verifying checksum(s) for jam
---> Extracting jam
---> Applying patches to jam
---> Configuring jam
---> Building jam
---> Staging jam into destroot
---> Installing jam @2.5_1
---> Activating jam @2.5_1
---> Cleaning jam

Time to continue the Mapnik install.

VMWare and keyboard input

gregs — Thu, 10 Jul 2008 01:07:03 +0000

This morning I fired my Windows XP VM on my mac and my keyboard input simply stopped working. After a couple of VM reboots, which had no effect, I did some googling. The first result suggested typing a few commands to determine what had disabled it:

PLAIN TEXT

CODE:

$ ioreg -l -w 0 | grep SecureInput
| "IOConsoleUsers" = ({"kCGSSessionSecureInputPID"=177,"kCGSSessionLoginwindowSafeLogin"=No,"kCGSSessionAuditIDKey"=0,"kCGSessionLoginDoneKey"=Yes,"kCGSSessionSystemSafeBoot"=No,"kCGSSessionOnConsoleKey"=Yes,"kCGSSessionUserIDKey"=501,"kSCSecuritySessionID"=11622192,"kCGSSessionUserNameKey"="gregstewart","kCGSSessionGroupIDKey"=20,"kCGSSessionConsoleSetKey"=0,"kCGSSessionIDKey"=256,"kCGSessionLongUserNameKey"="User"})
$ ps auxwwww | grep 177
user 177 7.8 9.2 652520 192788 ?? S 10:51pm 59:09.22 /Applications/Firefox.app/Contents/MacOS/firefox-bin -psn_0_110619
user 1155 0.0 0.0 599820 464 s001 S+ 10:44am 0:00.00 grep 177

According to the post the application that was blocking it was FireFox. "kCGSSessionSecureInputPID"=177 is the info you need to look for, where in my case 177 was the number I needed to use in the next command. Incredulous as I was, I closed FireFox and hey presto keyboard input was working again.

Hopefully this post will help others.