64 Bit Jungle

(No Ratings Yet)

 Loading ...

I love the fact that a huge amount of the applications I regularly use are available via the package manager, but sometimes, I like to install applications myself. Azureus is one such application - I wanted to install the latest x64 version, and utilise the x64 JRE I had installed for the x64 Eclipse IDE. Of course, it can easily be installed by running

sudo apt-get install azureus

(in Ubuntu) and everything is done automatically. But, this is how I installed it.

I had already installed x64 JRE (see 64 Bit Eclipse: Linux Installation, including PDT, WTP (WST), ATF, and MySQL (SQL Explorer Plugin)), but for the benefit of those who haven’t, don’t want to read that particular article, or just can’t be arsed scanning through it, here’s the procedure again (skip to —END x64 JRE INSTALL— if you don’t want to read this part!)

The 64 Bit JRE can be downloaded here (or use the direct link to the bin file). After the file downloaded to my desktop, I opened up a new Terminal Window (Applications -> Accessories -> Terminal), traversed to the directory I wanted to install it into, moved the file, made it executable, and ran it to install:

cd /usr/java
sudo mkdir 64
cd 64
sudo mv ~/Desktop/jdk-6u5-linux-x64.bin /usr/java/64/
sudo chmod a+x jdk-6u5-linux-x64.bin
sudo ./jdk-6u5-linux-x64.bin

If the “java” directory doesn’t exist by the way, it needs to be created first:

sudo mkdir /usr/java

Anyway, listing the directory

ls

should return

jre1.6.0_05

which is the directory containing the necessary Java binaries.

—END x64 JRE INSTALL—

The 64 Bit version of Azureus (currently v3.5.0.2) can be downloaded here. Once the archive had downloaded to my desktop, I unpacked it:

cd ~/Desktop
tar -xjvf Azureus_3.0.5.2_linux-x86_64.tar.bz2

As usual, I like to put applications (which don’t need compiling and installing) into /opt

sudo mv azureus /opt

Within the /opt/azureus folder, is a shell script for running the Azureus client called, funnily enough, azureus. However, to get it working with the 64 Bit JRE I had installed, I had to make a couple of minor adjustments to the script:

cd /opt/azureus
gksu gedit azureus

Line 5 contains a variable for the Java program directory:

JAVA_PROGRAM_DIR=""

so, I simply inserted the path to the JRE bin directory:

JAVA_PROGRAM_DIR="/usr/java/64/jre1.6.0_05/bin/"

saved the script, and closed the editor. I can now run the Azureus client by running this script:

/opt/azureus/azureus

Alternatively, it can be run from the Applications menu by creating an entry pointing to /opt/azureus/azureus - open System -> Preferences -> Main Menu, highlight “Internet”, and click “New Item”. Enter “Azureus” for the name, /opt/azureus/azureus for the Command, and change the icon to the Azureus logo by clicking on the Icon, and browsing to /opt/azureus/azureus, which will automatically list the images in the folder to choose from.

written by Hodge \\ tags: 64 bit, Azureus, BitTorrent, JRE

(No Ratings Yet)

 Loading ...

I wanted to see if I could take advantage of my Dual Core CPU during boot time, by enabling concurrent init.d scripts, in the hope this could improve (an already pretty fast) boot time. The implementation is pretty simple - first, I backed up /etc/init.d/rc

cd /etc/init.d/
sudo cp rc rc.BAK

then set about editing /etc/init.d/rc

gksu gedit /etc/init.d/rc

Actually, there isn’t much to edit - I just needed to change:

CONCURRENCY=none

to:

CONCURRENCY=shell

on line 24, save the file, and reboot. However, when I rebooted, there was a gnarly error caused by HAL (Hardware Abstraction Layer) failing to initialise. After some digging, I found a bug report, and a solution. The cause of the problem, and the solution is actually quite simple. At run level 2, HAL and DBus are set to start at the same time - in the /etc/rc2.d/ directory, both symbolic links have the same S12 prefix (S12hal and S12dbus):

ls -l
...snip...
lrwxrwxrwx 1 root root 14 2008-04-26 00:52 S12dbus -> ../init.d/dbus
lrwxrwxrwx 1 root root 13 2008-04-25 18:58 S12hal -> ../init.d/hal
...snip...

which causes a problem with concurrent init.d scripts, since they are now executed at the same time. HAL initialises slightly faster than DBus, but requires DBus in order to initialise, hence the “failed to initialize” error. The solution is equally simple. As suggested in the bug report, I changed the execution order of HAL. I had to do this via the recovery console, but so long as you don’t reboot after saving the /etc/init.d/rc file, it can be done via the GUI terminal:

sudo mv /etc/rc2.d/S12hal /etc/rc2.d/S13hal
sudo reboot

This time, there was no problem, and no error, since it ensures that DBus (S12dbus) initialises before HAL (S13hal).

If I still get problems in the future, I can always restore the old version of /etc/init.d/rc:

cd /etc/init.d
sudo cp rc.BAK rc

Coupled with boot profiling, this does speed up my boot time by shaving an extra few seconds away.

written by Hodge \\ tags: concurrent init.d, Dual Core, HAL, Ubuntu

(No Ratings Yet)

 Loading ...

Like most other Ubuntu users, I recently upgraded to 8.04 (Hardy Heron), but numerous power cuts, and a sketchy internet connection screwed up the upgrade process, resulting in a horribly drawn out process of reinstalling a fresh copy of 7.10, downloading and installing the updates, and finally the alternate CD for 8.04… but that’s another story for another time…

During this process, I found that the Ubuntu archive repository, http://archive.ubuntu.com/ubuntu/ was somewhat slower than usual. Thankfully, there are many mirrors available to download from - most are up to date with the latest packages. https://launchpad.net/ubuntu/+archivemirrors has an extensive list, so I looked for one with an “Up to Date” status, and edited my sources.list:

gksu gedit /etc/apt/sources.list

commented out the current archive site:

#deb http://archive.ubuntu.com/ubuntu/ hardy main universe multiverse restricted
#deb http://archive.ubuntu.com/ubuntu/ hardy-updates main universe multiverse restricted

and added the mirror:

deb http://ubuntu.positive-internet.com/ubuntu/ hardy main universe multiverse restricted
deb http://ubuntu.positive-internet.com/ubuntu/ hardy-updates main universe multiverse restricted

After saving the file, and starting the Update Manager, I simply had to click “Check” to retrieve the update information from the mirror. Alternatively, this can be done with the “Reload” button in the Synaptic Package Manager.

Simple, but effective, leading to much faster downloads, and you can always revert back to using archive.ubuntu.com by uncommenting the entries in sources.list, and commenting out/deleting the mirror entries.

written by Hodge \\ tags: repository mirror, Ubuntu

(No Ratings Yet)

 Loading ...

Sorry if you were expecting a substantial research report, but there really is no need for an in depth technical evaluation and comparison. No need to waste your time with specifications and benchmark results. No funky table with the pros and cons of each operating system. All you need do, is watch the following video.

Even if it’s satire, it’s more than enough reason to switch to Linux…

Cringe…

written by Hodge \\ tags: Hardy Heron, SP1, Ubuntu, Vista

(No Ratings Yet)

 Loading ...

I love Photography, and any oportunity I get, I try and take photos. I have a great camera, and living in the jungle, fantastic surroundings and photo oportunites everywhere I look. The only thing I’ve been lacking is a digital darkroom for Linux. OK, so we Linux users have GIMP, CinePaint (a fork from GIMP 1.0.4 specifically for photo/movie frame editing), and ufraw - a RAW digital image processor, along with a bunch of other great tools for image processing, but I just wanted to try something more. I’ve tried installing the trial version of Adobe Photoshop Lightroom with wine, but with no success, and as such, have continued my search for a viable Linux based digital darkroom…

A couple of days ago, I set up a makeshift studio at home so I could do a photoshoot of my wife and new baby (well, I say studio - it was in fact a couple of dark blankets I found about the house, no lighting, reflectors, or any of the expensive professional gear!). Once finished, I really wanted to process some of the better shots to send to my family, and so was determined to find something I could install and use on Linux.

Tenacity prevailed, and I finally discovered Lightcraft’s Lightzone - a Java based digital darkroom, with versions available for Mac, Windows and Linux! The Linux version is currently in Beta, but in all honesty, having used it for the past few days, I couldn’t tell. Installation is as simple as you can get - download the archive (registration is required, but it’s worth it), extract the files, enter the new directory, and run the LightZone executable:

tar -zxvf LightZone-3.4.tar.gz
cd LightZone
./Lightzone

After a dialog appears informing how many days of the trial are left, the splash screen displays as the program loads. The GUI is incredibly intuitive, and within minutes, I managed to process a couple of pictures worth sending to my family. When the application first opens, it’s a simple case of using the pane on the left to navigate to a directory containing photos. LightZone automatically generates thumbnails, and a larger preview of the chosen thumbnail with an option to edit. A single click on “Edit” brings up a whole array of processing options to play with.

After a few clicks, and mainly fumbling around the system, I managed to turn this raw image:

into a Black and White 10×8 Portrait that my Mum will love:

I’m incredibly happy with the results of a few minutes clicking and fumbling around an unfamiliar system! If this is what can be achieved by doing so, I’m really looking forward to getting my teeth into the system, and learning it’s many features - HDR (High Dynamic Range) support, Zone Systems, and many more.

Unfortunately however, I only have 9 days left on the Trial, since the Linux version is still in Beta, and therefore not available for purchase. I have no idea how much the Linux version will be when it’s finally released, but the Windows and Mac versions retail at $129.95 for the Basic version, and $199.95 for the Pro version. Unfortunately, both out of my price range for the time being (that’s a hell of a lot of money where I live!), but I’m certainly going to enjoy the Beta version while I can, and dream of when I can afford to buy the Pro version! Still, I’ll see if I can make some time to write a couple of tutorials and post them.

LightZone is a fantastic product. The only thing extra I would like to see, is a 64 Bit version.

written by Hodge \\ tags: darkroom, digital photography, Linux

(No Ratings Yet)

 Loading ...

I was cleaning up my computer today, and came across an old screen shot on my Windozzze XPoo partition. I took it back in the day, when Gmail was invite only and you had to enter a Captcha type string when you logged in…

Gotta love random strings!

written by Hodge \\ tags: Captcha

(No Ratings Yet)

 Loading ...

OK, so I have x64 Eclipse successfully installed and running with all the plugins I use for Web Application Development. But what about debugging? Sure, var_dump(), echo, print and so on are all valuable to me when debugging a script, but it’s always good to have more information.

Xdebug is a fantastic PHP extension, which is written by one of the PHP Core Developers, Derick Rethans. The current version is 2.0.3, and I set about installing it on my system, and integrating it into Eclipse PDT today.

Xdebug can be installed in a few different ways - by downloading the binaries from the site, compiling the source, or via PECL:

sudo pecl install xdebug

Some days, I just prefer to download compile the source, as it gives me more of an understanding of what is being installed and where, and this is one of those days:

cd ~/
mkdir xdebug
cd xdebug
wget http://www.xdebug.org/link.php?url=xdebug203
tar -zxvf xdebug-2.0.3.tgz
cd xdebug-2.0.3

The packages phpize and php-config are required to install Xdebug, and can be obtained by installing the relevant PHP development packages:

sudo apt-get install php4-dev

or

sudo apt-get install php5-dev

depending on the PHP version installed. After unzipping the Xdebug source, I ran

phpize

which output:

PHP Api Version: 20041225
Zend Module Api No: 20060613
Zend Extension Api No: 220060519

I then checked this against the table at http://www.xdebug.org/docs/install#phpize to see if my PHP version (5.2.3) was compatible with Xdebug - it matched up to the table’s 5.2.x PHP version row, so I went ahead and installed:

./configure --enable-xdebug --with-php-config=/usr/bin/php-config
make

which created a file xdebug.so in the modules subdirectory. This file needs to be copied (or moved) to the PHP Extension directory, which on my system is in /usr/lib/php5/20060613/. An easy way to find the PHP extension directory is to run:

locate mysql.so

ok, so I copied the xdebug.so to the extension directory:

sudo cp modules/xdebug.so /usr/lib/php5/20060613/

So far so good. Now PHP needs to be told about the extension, and to load it. This can be done by adding

zend_extension="/usr/lib/php5/20060613/xdebug.so"

to the php.ini file. However, on my Ubuntu system, the PHP extensions are activated by adding an .ini file to the /etc/php5/apache2/conf.d directory, for each extension installed. The .ini file is the extension_name.ini, so I created a file called xdebug.ini:

cd /etc/php5/apache2/conf.d
gksu gedit xdebug.ini

which for now, contains a single line:

zend_extension="/usr/lib/php5/20060613/xdebug.so"

After restarting the Apache server

sudo /etc/init.d/apache2 restart

I created a file called test.php in my Web Root directory, containing a call to the phpinfo() function:

<?php
phpinfo();
?>

and pointed my browser to http://localhost/test.php. Just before the “PHP Credits” section, is a small box containing information on Zend - and now, with a successful Xdebug installation, additional information on Xdebug:

The same information can be found by opening a Terminal and running

php -m

to output the loaded modules, and towards the end of the output, you should see

[Zend Modules]
Xdebug

alternatively, run

php -i | grep Xdebug

and if Xdebug has been installed successfully, you should see

with Xdebug v2.0.3, Copyright (c) 2002-2007, by Derick Rethans

Now, Xdebug needs to be enabled before any scripts can be debugged! So, in the php.ini file (or in my case, the newly created /etc/php5/apache2/conf.d/xdebug.ini file) I added the lines:

xdebug.remote_enable=On
xdebug.remote_host="localhost"
xdebug.remote_port=9000
xdebug.remote_handler="dbgp"

and restarted Apache again:

sudo /etc/init.d/apache2 restart

running

php -i | grep xdebug

in the Terminal, or using the test.php file containing phpinfo() shows that the new settings are being used, and Xdebug is active and running.

Configuring Eclipse PDT:

Setting up Eclipse PDT to use the Xdebug extension is pretty simple. In Eclipse PDT, I opened Window -> Preferences, then clicked on PHP, expanded the tree, and selected Debug. I Chose Xdebug from the pull down menu for the PHP Debugger, the “Default PHP Server” (should already be set to localhost), and then created a new PHP Executable option by clicking on the PHP Executables link next to the PHP Executable pull down menu.

In the PHP Executables dialog, I Clicked Add, filled in the name (PHP with XDebug), and entered the path to the PHP executable - on my system this is /usr/bin/php but if you don’t know, then in a terminal, run

which php

to find out where the php command is run from. I also entered the location of php.ini - again, on my system, this is /etc/php5/apache2/php.ini - and selected XDebug as the PHP debugger:

Clicked OK, then went back to the PHP -> Debug preferences screen, and selected the PHP Executable just created in the PHP Executable pull down. Finally, in the Debug -> Workbench Options option in the left, I selected “Never” for the “allow multiple debug sessions” option, since Xdebug does not support them.

Finally, I needed to set the Default Web Browser in Eclipse, to that when I debug a script, the output is sent to Firefox. Again in Preferences, I navigated to General -> Web Browser, and clicked “New”. It’s pretty straight forward stuff - entering a name and location - Firefox, and /usr/bin/firefox. Again, if you don’t know the location of the firefox binary, in a terminal run:

which firefox

With this done, and the preferences saved, I can now debug my scripts using Xdebug!

References:

http://www.xdebug.org/docs/install
http://www.eclipse.org/pdt/documents/XDebugGuide.pdf
http://devzone.zend.com/article/2803-Introducing-xdebug

written by Hodge \\ tags: Eclipse, PDT, Xdebug

(1 votes, average: 5 out of 5)

 Loading ...

NOTE, 04/08/08: This tutorial covers Eclipse Europa. If you would like to install the latest version of Eclipse 3.4 Ganymede, with PDT and SQL Explorer, take a look at my latest Tutorial: “64 Bit Eclipse 3.4 (Ganymede) IDE with PDT and SQL Explorer - Full PHP/MySQL Web Application IDE“.

I had tried once before to install the x64 (64 Bit) version of Eclipse IDE, about 8 months ago, but found it to be somewhat buggy and unstable. In the interim, I’ve been using the 32 Bit version of Eclipse PDT for my development stuff. Earlier this year (21/02/08) a new version of Eclipse 64 Bit was released, so I gave it a go today. So far, so good!

Unfortunately, there’s no 64 Bit PDT all-in-one, but I managed to install a 64 Bit equivalent by cobbling together the relevant packages available by using the Eclipse Update Manager system, after initially installing the latest version of Eclipse Classic 3.3.2 64 Bit.

I wanted to keep everything (or as much as possible) 64 Bit, so I also download and installed the 64 Bit JRE, which can be downloaded here (or use the direct link to the bin file). The method for installing the 64 Bit JRE is the same as the 32 Bit version - after the file downloaded to my desktop, I opened up a new Terminal Window (Applications -> Accessories -> Terminal), traversed to the directory I wanted to install it into, moved the file, made it executable, and ran it to install:

cd /usr/java
sudo mkdir 64
cd 64
sudo mv ~/Desktop/jdk-6u5-linux-x64.bin /usr/java/64/
sudo chmod a+x jdk-6u5-linux-x64.bin
sudo ./jdk-6u5-linux-x64.bin

If the “java” directory doesn’t exist, it needs to be created first:

sudo mkdir /usr/java

listing the directory

ls

should return

jre1.6.0_05

which is the directory containing the necessary Java binaries.

As with my previous 32 Bit installation, I wanted Eclipse to be installed in the /opt directory:

cd /opt
sudo mv ~/Desktop/eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz /opt
sudo tar -zxvf eclipse-SDK-3.3.2-linux-gtk-x86_64.tar.gz

then rename the eclipse directory:

sudo mv eclipse eclipse64

I also needed to get the newly installed Eclipse to run with the newly installed JRE - by default, the eclipse executable in the directory will try and detect Java and use whatever it finds, so I created a shell script:

cd eclipse64
sudo gksu gedit eclipse.sh

containing the following:

#!/bin/bash
PATH=/usr/java/64/jre1.6.0_05/bin:$PATH
/opt/eclipse64/eclipse

Now instead of running the eclipse executable, I run eclipse.sh (make sure it’s executable)

sudo chmod 755 eclipse.sh

before running

/opt/eclipse64/eclipse.sh

PDT and WTP Plugins

The first time I ran the new 64 Bit version, everything went well - it was fast, and seemed stable, so I went ahead and started installing all the additional plugins I needed (and still need…). Goto Help -> Software Updates -> Find and Install, and select “Search for new features to install”.Click on “New Remote Site” for each of the following:

• Name: PDT, URL: http://download.eclipse.org/tools/pdt/updates/
• Name: WTP, URL: http://download.eclipse.org/webtools/updates/
• Name: GEF, URL: http://www.eclipse.org/gef/updates/
• Name: EMF, IRL: http://www.eclipse.org/modeling/emf/updates/

Actually, there are only a couple of components required from the GEF (Graphical Editing Framework) and EMF (Eclipse Modeling Framework) packages to satisfy dependencies - WTP (Web Tools Platform) requires a package from GEF, and GEF from EMF…

After adding these, click on Finish - the Update Manager will then query any mirrors for the latest versions of the plugins. Once it has finished, a dialog appears, where it is possible to select the plugins to download and install. First, I selected PDT - the Update Manager then informed me that PDT requires files from WTP, so I tried clicking the “Select Requires” button, hoping that it would sort out the dependencies on my behalf. Unfortunately, nothing happened… So, I selected WTP manually, then expanded GEF -> Eclipse SDK R3.3.1 and Selected Graphical Editing Framework 3.3.1v20070814, then expanded EMF -> EMF SDK 2.3.2 and selected Eclipse Modeling Framework (EMF) - org.eclipse.emf.ecore 2.3.2v200802051830… I could then click “Select Required” to get the last few residual required dependencies… Phew…

Actualy, it still bugged me for dependencies for Java Persistence API contained in WTP, but by that stage I really couldn’t be arsed going through the process of adding more stuff to the Update Manager and potentially having to search for further dependencies, so I just deselected the three Java Persistence API files contained in WTP.

OK, with the dependencies sorted, I clicked Next, accepted the agreements, finished, and went to make, and drink a brew (that’s Tea) while the Update Manager downloaded and installed the requested stuff.

MySQL: SQL Explorer Plugin

Once everything had downloaded and installed, I restarted Eclipse. Everything looked good! Great, in fact. But I also wanted to install a few more plugins, including the MySQL SQL Explorer Plugin - which additionally requires, and depends on Eclipse DTP (Data Tools Project). Eclipse DTP has to be downloaded and installed manually, since there is no automated Update Site. So, I downloaded dtp_1.5.2_022008.zip to my Desktop, and set about extracting and installing the files:

cd ~/Desktop
mkdir DTP
mv dtp_1.5.2_022008.zip DTP
cd DTP
unzip dtp_1.5.2_022008.zip
cd eclipse
sudo cp -R features plugins /opt/eclipse64

If Eclipse is open, restart it. With the DTP installed, I could set about installing the SQL Explorer Plugin. The instructions for installing and configuring the SQL Explorer Plugin can be found in my previous article - Eclipse PDT and MySQL - SQL Explorer Plugin, since I don’t want to regurgitate information, just follow the link if you need to install it, and come back when it’s done.

Note: Actually, now I had the DTP installed, I could download and install the additional Java Persistence API in WTP! Same method: Update Manager, select WTP etcetera, etcetera…

ATF: AJAX Framework Toolkit

Once the SQL Explorer Plugin was installed, I had one final plugin - ATF (the AJAX Toolkit Framework). This can be downloaded as a Site Archive, and the zip file added to Eclipse’s Update Manager. Once downloaded, I opened the Update Manager in Eclipse (Help -> Software Updates -> Find and Install), and clicked on “New Archived Site”, to add a new locally archived site, calling it ATF, and pointing it to the freshly downloaded atf-incubation-SiteArchive-0.2.3M4-v200709141050.zip file. I discovered, however, that the site.xml file contained within the zipped site archive is somewhat out of date and the pointers within are directed to the wrong download locations, so I had to manually locate the additional dependent plugins - Mozilla XULRunner, and Mozilla JS. They can both be added as New Remote Sites to the Update Manager, by clicking on the “New Remote Site” button, and adding the following information:

• Name: Mozilla JS, URL: http://ftp.mozilla.org/pub/mozilla.org/js/eclipse/
• Name: XULRunner, URL: http://releases.mozilla.org/pub/mozilla.org/xulrunner/releases/1.8.1.3/contrib/eclipse/

The previously used EMF plugin is also required to satisfy a couple of dependencies, so I selected the ATF, Mozilla JS, XULRunner, and EMF plugins from the list, and clicked Finish. Once the “updates” were found, I selected XULRunner, Mozilla JS, ATF (I deselected the ATF -> Mozilla JS component though, since an updated version was to be downloaded and installed from the Mozilla Server), and also selected the required EMF components. Click through Next etc. to download and install. Once completed, I restarted Eclipse.

In the Window -> Preferences menu by the way, AJAX toolkits such as Script.aculo.us can be added to the ATF module.

Et Voila! I now have a working Eclipse 64 Bit version up and running! Finally!

Oh, if you want a desktop icon, just create a file on your Desktop called Eclipse.desktop,

cd ~/Desktop
gedit Eclipse.desktop

and add the following:

[Desktop Entry]
Categories=;
Encoding=UTF-8
Exec=/opt/eclipse32/eclipse.sh
Hidden=false
Icon=/opt/eclipse64/icon.xpm
Icon[en_US]=/opt/eclipse64/icon.xpm
Name=Eclipse
Name[en_US]=Eclipse
Terminal=false
Type=Application
Version=1.0

written by Hodge \\ tags: ATF, Eclipse, Eclipse 64 Bit, MySQL, PDT, SQL Explorer Plugin, WST, WTP

(No Ratings Yet)

 Loading ...

I recently installed Firestarter (a Firewall GUI for Linux - sometimes I just cant be arsed using CLI to configure iptables etc!), but I’ve noticed that when my system boots, it throws up the following error:

invoke-rc.d: initscript firestarter, action "restart" failed
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2

This is actually a bug with version 1.0.3-5, and the solution is pretty simple - to upgrade to version 1.0.3-6. However, I have Ubuntu 64 Bit installed, and unfortunately, 1.0.3-6 is not yet available in the repositories. Not worries - just a simple case of downloading the source tar ball, compiling, and installing.

First, I removed the currently installed version:

sudo apt-get remove firestarter

and downloaded the latest tar ball. Once this had downloaded to my desktop, I went through my usual routine of creating a new directory, moving the file, extracting… and so on:

cd ~/Desktop
mkdir firestarter
mv firestarter-1.0.3.tar.gz firestarter
cd firestarter
tar -zxvf firestarter-1.0.3.tar.gz
cd firestarter-1.0.3

Installation is pretty straightforward - although it’s always good to read the README and INSTALL files!

more INSTALL

So, configure, make, and install:

./configure --sysconfdir=/etc
make
sudo make install

However, the configure step threw out a few errors for me:

Package libgnome-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libgnome-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'libgnome-2.0' found Package libgnomeui-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libgnomeui-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'libgnomeui-2.0' found Package gnome-vfs-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `gnome-vfs-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'gnome-vfs-2.0' found Package libglade-2.0 was not found in the pkg-config search path. Perhaps you should add the directory containing `libglade-2.0.pc' to the PKG_CONFIG_PATH environment variable No package 'libglade-2.0' found
configure: error: Library requirements (libgnome-2.0 >= 2.0.0
libgnomeui-2.0 >= 2.0.0
gtk+-2.0 >= 2.4.0
gnome-vfs-2.0 >= 2.6.0
libglade-2.0 >= 2.3.6)

which basically means that I didn’t have some of the necessary development libraries installed required to compile the binaries. No real problem, and easy enough to solve by, well, installed in the required packages:

sudo apt-get install libgnome-dev libgnomeui-dev libgnome-vfs-dev libglade2-dev

This process also had to download an additional 50 packages to meet the dependencies of the above four packages (and there were probably some sub dependencies there too…)

Anyway, the configure process ran smoothly after installing the required dev libraries, so I could then run

make
sudo make install

to compile and install the new binaries.

It’s possible to have Firestarter run as a system service, by copying the fedora.init file from the install directory to /etc/init.d and renaming the file to firestarter, then enabling the script:

sudo cp fedora.init /etc/init.d/firestarter
sudo chkconfig firestarter reset

However, since I had previously installed Firestarter, all the relevant scripts and symbolic links were already in place. All I had to do was make a minor change to the /etc/init.d/firestarter script:

cd /etc/init.d
cp firestarter firestarter.old
gksu gedit firestarter

and changed the line

[ -x /usr/sbin/firestarter ] || exit 0

to

[ -x /usr/local/bin/firestarter ] || exit 0

so that the script would point to the new installed binary. That’s it.

written by Hodge \\ tags: firestarter, firewall

(No Ratings Yet)

 Loading ...

I’m just playing around with a new theme for the site at the moment. I like this i3Theme, since I can split the side bar up into two sections - makes organising the side content a little easier - just need to design some kind of logo to go with the new theme

written by Hodge \\ tags: Wordpress theme