All posts

Installing AucTeX on EmacsW32 on Win7/64bit

August 17, 2010
Today I had to install AucTeX to use on my Win7/64 machine under EmacsW32. I found the basic instructions here: http://www.sturmnet.org/blog/2007/09/01/installing-auctex-in-emacsw32, but I had to modify them a bit (in particular, I am using tetex installed from cygwin instead of MiKTeX). Here are the commands I used:

$  mkdir -p /usr/local/share/texmf
$ ./configure --prefix='c:/Program Files (x86)/Emacs/emacs' --with-texmf-dir='/usr/local/share/texmf' --with-lispdir='c:/Program Files (x86)/Emacs/emacs/site-lisp'
$  make
$  make install

I then added the following lines to my C:\Program Files (x86)\Emacs\site-lisp\site-start.el file:

Updated server and service setup

August 16, 2010

(a friend asked me about my online setup, and I wrote the text below. Then I realized it would also make an interesting blog post, and I just copied and pasted it, with minimal editing, into an email to posterous. This is why I love posterous, it makes posting so easy)

For my setup, I have a hodgepodge of stuff all aggregated under the zzamboni.org domain. I wrote a blog post about my setup some time ago: http://blog.zzamboni.org/server-less-does-not-mean-service-less

Anchoring Effect « You Are Not So Smart

July 30, 2010

You walk into a clothing store and see what is probably the most bad ass leather jacket you’ve ever seen.

You try it on, look in the mirror and decide you must have it. While wearing this item, you imagine onlookers will clutch their chests and gasp every time you walk into a room or cross a street. You lift the sleeve to check the price – $1,000.

Well, that’s that, you think. You start to head back to the hanger when a salesperson stops you.

Layer 8: The exception IS the rule

July 9, 2010
Whenever you look at a firewall rule, half the time you’re going to be asking yourself, “Why is that there?  Did *I* put it there?  Do we still need it?”  It would sure be nice if the explanation were right there, as a comment that could be version-tracked, exported into nice reports, searched on, and placed in a standard format that would be compatible with other exception entries in other tools.  (Kind of like a syslog for exceptions.)  It would be nice if you could mark a scanner finding as, “We KNOW it’s there.  We’re not going to fix it.  Just for these two machines, STOP REPORTING ON THIS.”)
via layer8.itsecuritygeek.com

Insightful article. I can't count the number of times I have asked myself exactly this, and hoped for a good, INTEGRATED way of keeping track of these exceptions.