A few days ago, Linode.com announced native IPv6 roll out in their datacenters. Now, while I haven’t wrote about Linode in the past 6 months, I am still a happy customer. I am documenting the steps I took to migrate away from my HE.net tunnel. Set the TTL low on any DNS addresses that you will be changing. Ideally, do this a fair amount ahead of time. Send in a support ticket to get your /64 allocated.
It has been awhile since I’ve posted about what I’ve been doing with Gentoo Linux. So, here is a general update for the team that I have been spending most of my time with. You may have seen the Bugzilla upgrade that Christian was working on. Gentoo moved from the bottom of the list provided from one of the upstream devs to the top of the list. (As of April 2011) I finally put an idea of mine into reality of graphing the number of “emerge –sync’s” against the rsync.gentoo.org rotation.
As of writing today, my Android powered phone (Droid X) cannot send SMS messages to some people, but receive messages fine. This is because my address book has “+1” on some people’s numbers. Solution: Add/edit a number without the “+1” – in a connected world, I don’t even bother to “save” phone numbers, they get synced to me from third party sources (facebook). In this case, synced in such a way that it won’t work.
Scenario: You need to setup a service that requires ssh access to a remote host, possibly/probably by the root user. This service needs to run at regular intervals and it is critical that it works without a human entering a passphrase (even once). Solution: The obvious solution that comes to mind is a ssh key. But a password-less key that allows root login? RED FLAG. However, there is a way to accomplish this without allowing a root login completely.
The problem: % dmesg | grep -i micro Atom PSE erratum detected, BIOS microcode update recommended Atom PSE erratum detected, BIOS microcode update recommended microcode: CPU0 sig=0x106c2, pf=0x4, revision=0x208 microcode: CPU1 sig=0x106c2, pf=0x4, revision=0x208 microcode: Microcode Update Driver: v2.00 , Peter Oruba I found out that some recent kernel that I loaded at an unknown time, was able to point out that I had ‘old’ microcode for my processor on my Aspire1 ZG5.