NeoArch

I just switched my workstation over to a static IP setup. It’s an Ubuntu machine, and I ran into a little snag. Every time that I tried to sudo any command, it returned the following error:

sudo: unable to resolve host MyComputersName

If you have this problem, it’s an easy fix. Edit your host file (sudo vim /etc/hosts). You probably have your machine name configured as localhost, 127.0.0.1, or 127.0.1.1. Whatever it is, change the ip address associated with the machine name to the new static ip address. Ubuntu will stop screaming at you.

Just today, I was working on converting a Proliant ML350 G2 server from running Windows Server 2000 to a Linux distribution. I noticed several people had this same problem with various flavors of Linux, and I did not find a legitimate workaround that did not involve a noapic option. I was getting an error that involved this line: MP-BIOS bug: 8254 timer not connected to IO-APIC.

I did find a workaround. It’s not that creative. I went to the HP/Compaq website and ran all the BIOS and firmware updates. The install went through without issue after that.

This post is just an FYI for those trying to use Capistrano on Ubuntu Feisty and running into the same problem I had. I had trouble finding specific information on the topic, thus this post.

I recently tried to use Cap on Ubuntu, and it would not work. I already had ruby and gems installed, having installed them using apt-get. I installed capistrano using the gem install capistrano. I could run gem list and capistrano was installed. All of my other gems worked fine.

When I checked the status of Capistrano using cap -h, I go the error bash: cap: command not found. After doing some searching, I found out how to fix it. Open ~/.bashrc using your favorite text editor. At the end of the file, add these lines:

#The following sets the path for Capistrano
export PATH=$PATH:/var/lib/gems/1.8/bin

Save the file and reboot. Capistrano should work now.