gregs

os x

Recursive delete

by gregs on Mar.22, 2010, under *nix, debian, os x

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

CODE:
  1. rm -rf `find . -type d -name .svn`

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

2 Comments more...

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

by gregs on Apr.06, 2009, under *nix, mac, os x

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

CODE:
  1. sudo port install icu jam
  2. 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
  3. 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:

CODE:
  1. sudo port install icu jam
  2. --->  Building icu
  3. 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
  4. 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:

CODE:
  1. sudo port clean --work icu
  2. --->  Cleaning icu
  3. sudo port clean --work jam
  4. --->  Cleaning jam
  5. sudo port install icu jam
  6. --->  Fetching icu
  7. --->  Verifying checksum(s) for icu
  8. --->  Extracting icu
  9. --->  Configuring icu
  10. --->  Building icu
  11. --->  Staging icu into destroot
  12. --->  Installing icu @4.0_0
  13. --->  Activating icu @4.0_0
  14. --->  Cleaning icu
  15. --->  Fetching jam
  16. --->  Attempting to fetch jam-2.5.tar from http://distfiles.macports.org/jam/2.5
  17. --->  Verifying checksum(s) for jam
  18. --->  Extracting jam
  19. --->  Applying patches to jam
  20. --->  Configuring jam
  21. --->  Building jam
  22. --->  Staging jam into destroot
  23. --->  Installing jam @2.5_1
  24. --->  Activating jam @2.5_1
  25. --->  Cleaning jam

Time to continue the Mapnik install.

3 Comments more...

VMWare and keyboard input

by gregs on Jul.09, 2008, under *nix, mac, os x, vmware

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:

CODE:
  1. $ ioreg -l -w 0 | grep SecureInput
  2. |   "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"})
  3. $ ps auxwwww | grep 177
  4. user 177   7.8  9.2   652520 192788   ??  S    10:51pm  59:09.22 /Applications/Firefox.app/Contents/MacOS/firefox-bin -psn_0_110619
  5. 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.

1 Comment more...

Looking for something?

Use the form below to search the site:

Still not finding what you're looking for? Drop a comment on a post or contact us so we can take care of it!