Tag Archives: CentOS

Thunderbird and Firefox 10 in CentOS and RHEL

CentOS 6’s default repository still only has Firefox/Thunderbird version 3.1, and a lot of newer and greater versions has been released since then.

To begin with, make sure you have the older version of Firefox/Thunderbird installed. This is necessary, as we are going to use their launch scripts as a template to create the launch scripts for the newer version.

To shorten things up, I will refer to Thunderbird as TB, and Firefox as FF. For the most part, I will refer to TB instead of both TB and FF. All you have to do is change where I write ‘thunderbird’ to ‘firefox’ and it will most likely work. To begin with, you want to download the latest version of Thunderbird or Firefox.

  • 32 bit TB:
    wget 'http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/10.0-real/linux-i686/en-US/thunderbird-10.0.tar.bz2'
  • 64 bit TB:
    wget 'http://releases.mozilla.org/pub/mozilla.org/thunderbird/releases/10.0-real/linux-x86_64/en-US/thunderbird-10.0.tar.bz2'
  • 32 bit FF:
    wget 'http://releases.mozilla.org/pub/mozilla.org/firefox/releases/10.0/linux-i686/en-US/firefox-10.0.tar.bz2'
  • 64 bit FF:
    wget 'http://releases.mozilla.org/pub/mozilla.org/firefox/releases/10.0/linux-i686/en-US/firefox-10.0.tar.bz2'

Untar and unzip the file you just downloaded (as said before, name may vary with the product you are installing). Afterwards, delete the tar file, which is no longer necessary.

tar xf thunderbird-10.0.tar.bz2
rm -rf thunderbird-10.0.tar.bz2

The simplest way is to delete the current TB/FF install, and move the newly downloaded files to the old directory. This command will vary for 32 and 64 bit systems. IMPORTANT: For Firefox, change the number 3.1 to 3.6 for both architectures. As for the commands, for 32 bit:

rm -rf /usr/lib/thunderbird-3.1/*
mv thunderbird/* /usr/lib/thunderbird-3.1/

For 64 bit systems:

rm -rf /usr/lib64/thunderbird-3.1/*
mv thunderbird/* /usr/lib64/thunderbird-3.1/

Congratulations! You are more or less done. Now, you may want to get rid of the empty FF/TB folder by running the command:

rm -rf thunderbird

That’s pretty much all. Running command ‘thunderbird’ or going to ‘Applications -> Internet -> Thunderbird Email’ will launch the newly installed version!

Beyond TB/FF 10, the ‘automatic upgrade’ feature should kick in. As you can see in the two screenshots above, TB and FF will automatically look for new versions, and will automatically upgrade when they exist. This way, you can run much newer versions than those found in the CentOS/RHEL repo.


Setting Up CentOS/Fedora/RHEL with Tunnelbroker

Tunnelbroker allows users with only IPv4 access to access the internet via IPv6 via a tunnel, hence its name. To use Tunnelbroker, you will first need an account from their website. Make sure to use your IP address under IPv4 Endpoint and select the location closest to you for a lower latency.If you plan to use this tunnel on a remote server, choose the most relevant settings for that server.

After proceeding, you will have an IPv6 tunnel setup for you. Now, you will have to edit the configuration files.

To configure your computer/VPS to begin using the tunnel, edit the /etc/sysconfig/network file. You will need to add the following two lines. In some installs, you may have NETWORKING_IPV6=no, in which case you just change the no to the yes. This should be pretty self explanatory.

IPV6_DEFAULTGW=<Server IPv6 Address without /64>

To complete configuring your computer to route IPv6 through tunnelbroker, you will have to create /etc/sysconfig/network-scripts/ifcfg-sit1, with the following content:

IPV6TUNNELIPV4=<Server IPv4 Address>
IPV6ADDR=<Client IPv6 Address with /64>

For these changes to take effect, run the following command to restart your network.

service network restart

To test that IPv6 is working, you can ping one of the sites with IPv6 enabled (such as this site). Pinging IPv6 addresses use the ping6 command, rather than the traditional ping command.

ping6 www.fusionswift.com
ping6 ipv6.google.com
ping6 www.v6.facebook.com

Setup VNC on CentOS/RHEL 6

The process of setting up VNC (and GNOME Desktop) is slightly different between CentOS 5 and 6. When using the CentOS 5 VNC installation method for CentOS 6, you will often get the error ‘Group GNOME Desktop Environment does not exist’ while attempting to install GNOME. This article will go over the process required to successfully setup VNC and GNOME on CentOS 6. This tutorial should work whether you are using a VPS, or using a Netinstall of CentOS 6. To begin with, you should use yum to download the GNOME Desktop environment. If you wish to use KDE instead of GNOME, install “KDE Desktop” instead of “Desktop”.

yum groupinstall "Desktop"

The typical yum installation process will take place. After the Desktop group has been successfully installed, install the TigerVNC server and the font required for CentOS 6 to work.

yum install tigervnc-server xorg-x11-fonts-Type1

Afterwards, the GNOME Desktop Environment should have been completed. You want to start the VNC server at that point. Login to the user you want to use the desktop for (typically a user other than root), and run the command:


On your first time running the command, you will be asked to choose a password for VNC for the account After the password is set, you will see something like the following:

New 'fusionswift.com:1 (root)' desktop is fusionswift.com:1

Creating default startup script /root/.vnc/xstartup
Starting applications specified in /root/.vnc/xstartup
Log file is /root/.vnc/fusionswift.com:1.log

Note for you, your VPS’s hostname will be in place of ‘fusionswift.com’. After the hostname, you will see that number. Add that number to 5900, and that will be the port VNC will be running on. In the above example, port 5901 will be used. To stop the vnc server, use the command, where number is the number you added to 5900:

vncserver -kill :number