One of the benefits of using Linux is its package-management systems, whatever the flavour of Linux you may use. The one drawback is when there are times that you want or need an update before it can be pushed out of the distribution's update channels. The application's inbuilt update mechanism is likely disabled, and the distro maintainers are rightly testing the update --- but you need to have that update today.
Typically that would involve going to the application's website and downloading the update, but for Firefox and Thunderbird users, Mozilla hides away its x86_64 builds on its ftp server; if you go to the regular download page and click on Linux, you will be given the 32-bit build.
The magic url to get at the 64-bit goodness is:
For instance, the URL for the UK English build of Firefox 8 is ftp://ftp.mozilla.org/pub/firefox/releases/8.0/linux-x86_64/en-GB/.
Once you have downloaded the archive and extracted it, you'll need to run the program. Now you could simply run directly the executable in the directory "./firefox", or we could use a script that Mozilla provides to set up the environment variables: ./run-mozilla.sh ./firefox
The only caveat for using the run-mozilla script is to make sure you use "./firefox", as otherwise it will call the old install of Firefox that lives in your PATH.
This doesn't mean that if we have a 32-bit executable, then we cannot run it on a 64-bit distribution, but it does mean that some extra installs are needed. Here's the list of packages that I needed to install on my Fedora 16 machine to get 32-bit Firefox working:
These packages are all duplicates of 64-bit packages already on the system.
Running a build directly from Mozilla will remove a certain level of integration with your desktop environment; for instance, I found that Thunderbird did not use GNOME 3 notifications, as it preferred its own mechanism for that. Other plug-ins, such as Flash, could also not be found by the downloaded version of Firefox.
I restored the plug-ins by making a symbolic link from the plug-ins directory to the directory where Firefox was installed:
ln -s /usr/lib64/mozilla/plugins ~/firefox/
After some intense discussions earlier this week with Firefox about its latest fetish for eating my system's memory, I found the Firefox update not as hungry as its predecessor --- which is well worth the minor issues of not having a distribution's official approval.
Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining the company as a programmer.Leaving CBS Interactive in 2010 to follow his deep desire to study the snowdrifts and culinary delights of Canada, Chris based himself in Vancouver and paid for his new snowboarding and poutine cravings as a programmer for a lifestyle gaming startup.Chris returns to CBS in 2011 as the Editor of TechRepublic Australia determined to meld together his programming and journalistic tendencies once and for all.In his free time, Chris is often seen yelling at different operating systems for their own unique failures, avoiding the dreaded tech support calls from relatives, and conducting extensive studies of internets -- he claims he once read an entire one.