Sometimes it is something to do with Apple system logs. You can clear them through this:

It works for me and I’m a happy user again, now the prompt in Terminal starts quickly when I start a new Terminal tab. Hope it helps.

PHP 4 and MySQL 4 End of Life Announcement

First up, the announcement that developers really care about. WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4.

For WordPress 3.2, due in the first half of 2011, we will be raising the minimum required PHP version to 5.2. Why 5.2? Because that’s what the vast majority of WordPress users are using, and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the Drupal and Joomla projects will be supporting in their next versions, both due out this year.

Finally!

You can change the source using:

This is now my /etc/apt/sources.list:

For Windows XP:

For Windows Vista or Windows 7:

In my case (email removed), it is found in “C:\Users \kahwee \AppData \Local \Microsoft \Messenger \something@example.com \ObjectStore \CustomEmoticons”.

For Mac OS X (Snow Leopard)’s Microsoft Messenger:

In my case, it is found in “/Users /kahwee /Documents /Microsoft User Data /Microsoft Messenger Data /something@example.com /ObjectStore /CustomEmoticons”

You can backup your custom emoticons by copying the directory to your flash drive or something. As far as I know, you cannot transfer Mac OS X’s Microsoft Messenger custom emoticons to your Windows’ Live Messenger and vice versa.

Ah, but there’s a catch

No. Once I did that I spend the next 30 minutes trying several commands to recover it, such as svn revert and svn update. They don’t work because the current directory’s .svn folder is still there and it’s just silly SVN’s way of knowing its there. Every command to revert led me, falsely, to believe my folders are all still there.

So I downloaded an entire new copy of the files I just deleted and put them back. That failed as the files I have restored manually don’t have the .svn folders. I tried committing the restored copies and the SVN server will just say the “Commit failed” with the reason “Server sent unexpected return value (405 Method Not Allowed) in response to MKCOL request for ‘…’”.

Don’t tell me what I can’t do!

Well… The thing is I wasn’t convinced. In an act of folly I deleted the parent directory which now resulted in the whole project just dead basically. Fantastic.

I should add that at this moment it all came back to me. I am certain this SHITuation happens to me at least a dozen time especially when I’m half awake.

As least Git doesn’t have that issue. Every time I use SVN, I have this feeling I’m walking on thin rope fearing to offend the Tiki gods. I guess I’m just not smart enough for SVN.

There, here is it. The rest of the code very well deserves to be deleted. Unpresentable, at best.

I can never figure out why I can’t install Twisted. In the end I give up. Don’t have much time left. Tick tock tick tock. I am using Ubuntu 10.04.

If you’re on NetBeans 6.7, I urge you to upgrade. If you aren’t a NetBeans user, do give NetBeans a chance. It’s (probably) slower and Java-ish but the excellent code completion support more than made up for it. Oh yeah, and it’s free too.

Try NetBeans 6.8.

Richard Stallman Eats Something From His Foot

During a lecture Q&A session Richard Stallman appears to pick something off his foot or toe, places it in his mouth and chews on it. Disgusting!

Introducing Google Public DNS: A new DNS resolver from Google

Today, as part of our efforts to make the web faster, we are announcing Google Public DNS, a new experimental public DNS resolver.

The DNS protocol is an important part of the web’s infrastructure, serving as the Internet’s “phone book”. Every time you visit a website, your computer performs a DNS lookup. Complex pages often require multiple DNS lookups before they complete loading. As a result, the average Internet user performs hundreds of DNS lookups each day, that collectively can slow down his or her browsing experience.

• Speed: Resolver-side cache misses are one of the primary contributors to sluggish DNS responses. Clever caching techniques can help increase the speed of these responses. Google Public DNS implements prefetching: before the TTL on a record expires, we refresh the record continuously, asychronously and independently of user requests for a large number of popular domains. This allows Google Public DNS to serve many DNS requests in the round trip time it takes a packet to travel to our servers and back.
• Security: DNS is vulnerable to spoofing attacks that can poison the cache of a nameserver and can route all its users to a malicious website. Until new protocols like DNSSEC get widely adopted, resolvers need to take additional measures to keep their caches secure. Google Public DNS makes it more difficult for attackers to spoof valid responses by randomizing the case of query names and including additional data in its DNS messages.
• Validity: Google Public DNS complies with the DNS standards and gives the user the exact response his or her computer expects without performing any blocking, filtering, or redirection that may hamper a user’s browsing experience.

(Source: Google)

Just use the following name servers:

Nice numbers. They got those from Level 3.