the body of a very slow loop
So you just installed Growl, eh? Wait! Before you unmount that .dmg, don’t forget to install growlnotify from the Extras directory.
cd /Volumes/Growl/Extras/growlnotify
sudo install.sh
If you get a permission denied error you might also need to do this:
sudo ln -s /usr/local/share/man /usr/local/man
Ok but why am I doing all of this? Check it out:
growlnotify --appIcon Xcode
-m "growlnotify has finished building" Build Complete
Today I installed an update to Outlook 2007 and was instructed to reboot my PC. I’ve pretty much had it with Windows and rebooting.
I can change freaking device drivers on my Linux boxes without a reboot. And that system was implemented by a loosely affiliated group of hairy communist volunteers (heh).
Can anyone explain the Windows behavior to me? I have some guesses, but nothing worth promulgating. If this behavior is some kind of tradeoff, what’s the upside? I’m missing it.
I can replace the binary of a running Linux executable — no problemo. Subsequent invocations of the program will read the new binary. Under the hood it’s all inodes and reference counting.
On my Vista box, a mere open CMD prompt can stop me in my tracks. I flail helplessly around, closing anything and everything which is open, clicking Retry, until the “in use” dialog goes away.
Update: It’s seems that a lot of pain is caused by Window’s read locks. Often times a file is kept open by some background process, preventing me from accomplishing some task. If you run into a problem that smells like a read lock, I recommend killing the following with extreme prejudice: anti-virus programs, desktop search programs, and mspdbsrv.exe
University of Washington has a pretty cool Crypto course online. Lecture videos, slides… it’s all here.
(Thanks, Preston)
My click-tastic Lexmark was built back in the olden days, before the Windows key existed. Thankfully, I have this useless Caps Lock key just begging to be pressed.
Name: Scancode Map
Value: 00 00 00 00 00 00 00 00 02 00 00 00 5b e0 3a 00 00 00 00 00
CNet News wonders why, Despite its aging design, the x86 is still in charge.
The article includes this quote from Simon Crosby, CTO of XenSource:
There’s no reason whatsoever why the Intel architecture remains so complex. There’s no reason why they couldn’t ditch 60 percent of the transistors on the chip, most of which are for legacy modes.
Wow. 60%? What a huge waste! Could that really be true? Lets take a look at a random K8 die shot from the inter-web:
Hmm. See that highly regular pattern that comprises the right half the chip? That would be cache.
Lets assume that Crosby meant 60% of the other part. You know, the not-cache stuff. Even if we are most charitable, he still wrong. We could perhaps simplify the front end of the chip (marked above as “Fetch Scan Align Micro-code.”) Still, much of that section is for the branch predictor and TLB, which might be good to keep around.
If I were going to invent a number, I’d have picked something much closer to 1%.
Latest Comments
RSS