$ hexdump /mach_kernel | head -1
0000000 feed face 0000 0012 0000 0000 0000 0002
[1]234 .. 45>>

2010.08.16 - 16:02 | patrick

MC-A-Fair


We survived the Montgomery Fair! Our menu consisted of:

2010.08.14 - 05:41 | patrick

Sky


Saw a shooting star ... beautiful. ' Hope my wish comes true.

2010.07.28 - 22:27 | patrick

*emacs


Finally a nice Emacs command: M-x viper-mode

2010.07.01 - 16:36 | patrick

GitX


While I am generally speaking a terminal fan, I started to like GitX, an OS X git GUI.

2010.06.08 - 04:11 | patrick

iOS


Just why did Apple decide to rename "iPhone OS" to "iOS"?
This will make searching for Cisco IOS literature and tips & tricks a pain!

2010.05.19 - 23:32 | patrick

Print vs. Display


Smart: "Print color output is different than screen color output because of one huge reason: print is subtractive output, while a light source like a monitor or the sun is additive output." -- Comment, AVSForum

2010.05.07 - 23:35 | patrick

What I am doing...


This Federal News Radio podcast covers part of my current work.

2010.04.29 - 15:55 | patrick

ctags & vim


The problem with Exuberant Ctags is that .h are by default C++, not C. Consequently, letting Ctags read only the header files is not enough - unless you want to have missing exports. An easy solution is to add the following definition to your "global" Makefile:
CTAGS_OPTS = -f .tags \
    --fields=+aS --c-kinds=+p --extra=+q \
    --langmap=C:.c.h --totals
Your directory-specific Makefile will look like this:
tags:
  @ctags $(CTAGS_OPTS) *.h $(SOME_OTHER_DIR)/*.h
Obviously, you want vim (and OmniCppComplete) to look for your new ".tags". Just add the following to your .vimrc:
set tags=.tags;$HOME
The ";" at the end tells vim to start looking for a ".tags" in the current directory, and if not found to go up one level, etc.
all rights [r] belong to us.