My son turned one recently. Our birthdays are in the same month, just a few days apart.
His birthday present to me was to sit on my lap at bedtime (as normal), while I read Goodnight Moon to him (as normal), carefully flipping the board book's pages in time to my reading (a first).
Sometimes it is a chore to be a parent. Sometimes it is a joy.
On his birthday it was a quiet delight.
I stayed at the Grand Tower Hotel in Hong Kong a great while back (well before I started this weblog), and chuckled when I read the Engrish descriptions of some of the movies available.
A mogul uses his media power to jack up another world war and even challenges the course of history. James Bond breaks the plan of the culprit and severely brings down the rivals.
An incredible experiment has altered thousands of alien DNA being resurrected. To combat with the alien menace, Ripley teams up a group of scientists to terminate the chaotic conflict.
Almost as good as All your base are belong to us.
I followed the directions in HOWTO: Cleaning up all those unnecessary junk files... - Ubuntu Forums to "clean up" my hard drive (they did work nicely, freeing almost 1.5GB), but on the next reboot, when I loaded Opera 9.27, I received this error message:
ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored. /usr/lib/opera/9.27-20080331.6/opera: error while loading shared libraries: libqt-mt.so.3: cannot open shared object file: No such file or directory
I followed the first set of directions from Opera on 64-bit (again, sigh) (ubuntuforums.org), which did not fix it, then added the first recommendation, which did.
Here is the magical sequence that restored Opera on my AMD64 system running Kubuntu 6.06.1 LTS:
aptitude install ia32-libs ia32-libs-gtk lib32asound2 linux32 ia32-libs-kde
For your edification, here is another way of installing Opera 32-bit on a 64-bit system: Opera 9 on Ubuntu Linux with AMD64
Just had this error:
SSH_AUTH_SOCK in environment is invalid
when I rebooted and my .bashrc automatically loaded keychain.
The solution:
$ keychain -k all # reload keychain
