for dir in `ls`;do cd $dir; tar -cvzf $dir.tar.gz *;mv $dir.tar.gz ..; cd ..;done

This will run an ls command, and temporarily save the output for use in the For loop. The code loops through each part of the ls output, moves into the current directory (assuming it is a directory), creates the archive and moves the archive file to the parent directory, before moving itself to the parent directory to begin again with the next part of the ls output.

So, for example, if you have the following directory structure:

/home
--username
----stuff_to_archive
------dir-to-archive1
------dir-to-archive2
------dir-to-archive3
------dir-to-archive4
------dir-to-archive5

and you wish to archive dir-to-archive1 through dir-to-archive5, and all the contents therein, you would run:

cd /home/username/stuff_to_archive
for dir in `ls`;do cd $dir; tar -cvzf $dir.tar.gz *;mv $dir.tar.gz ..; cd ..;done

The code will loop through each directory and archive its contents into a file named after the directory (e.g. dir-to-archive1.tar.gz), leaving you with:

/home
--username
----stuff_to_archive
------dir-to-archive1
------dir-to-archive1.tar.gz
------dir-to-archive2
------dir-to-archive2.tar.gz
------dir-to-archive3
------dir-to-archive3.tar.gz
------dir-to-archive4
------dir-to-archive4.tar.gz
------dir-to-archive5
------dir-to-archive5.tar.gz

If you want to use ZIP instead, then run:

for dir in `ls`;do cd $dir; zip $dir *;mv $dir.zip ..; cd ..;done

or replace the archiver command with whatever you want to use to compress the directory contents.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

As much as I love the i3Theme, I’m getting fidgety, and feel like dressing 64bitjungle up in a new outfit. I’m just making some tweaks and changes to the new theme, trying to get everything the way I want it – could take a couple of hours, or a couple of days. We’ll see!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Thanks for your support!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

32 Bit users

32 Bit users need only download the precompiled deb from one of the MySQL Mirrors, and once downloaded, the deb can be installed by opening a Terminal and running the following:

sudo dpkg -i mysql-workbench-oss-5.1.9-1_i386.deb

64 Bit users

To compile MySQL Workbench from source, a bunch of dependencies need to be installed, which can be done easily by running the following in a Terminal:

sudo apt-get install build-essential autoconf automake libtool libzip-dev libxml2-dev libsigc++-2.0-dev libglade2-dev libgtkmm-2.4-dev libglu1-mesa-dev libgl1-mesa-glx mesa-common-dev libmysqlclient15-dev uuid-dev liblua5.1-dev libpixman-1-dev libpcre3-dev libgnome2-dev libgtk2.0-dev libpango1.0-dev libcairo2-dev python-dev

The source package can be downloaded once again from one of the MySQL Mirrors. As usual, I downloaded to my Desktop, and ran the following to compile and install:

cd
mkdir mysqlwb-src mysql-workbench
mv Desktop/mysql-workbench-oss-5.1.9.tar.gz mysqlwb-src
cd mysqlwb-src
tar -zxvf mysql-workbench-oss-5.1.9.tar.gz
cd mysql-workbench-oss-5.1.9
./autogen.sh
make install DESTDIR=/home/<username>/mysql-workbench

I’m using the DESTDIR option, since with Workbench being in Beta, I don’t really want it installing system wide.

Unless you’re lucky enough to have a machine with ridiculous specs, this will take a while – so go make a brew, coffee, smoke a cigarette, or [instert short term recreational activity here], and come back in a few.

No, really – it takes a long time…

Once installed (took a long time, eh?), running it is easy – simply navigate to the installation directory and run the executable from the Terminal:

cd ~/mysql-workbench/usr/local/bin
./mysql-workbench

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

All good.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Thanks to all my valued readers for your loyalty and patience!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The script itself, can be downloaded here: export_amarok_covers. Simply right click and save it to the Desktop.

System Prerequisites

export_amarok_covers requires Python, python-dev and if your Amarok database is in MySQL, the Python’s MySQL libraries and connectors, as well as python-setuptools which contains scripts such as easy_install. These are easy to set up in Debian/Ubuntu systems. From a Terminal, run:

sudo apt-get install python python-dev python-mysqldb python-setuptools

Python Libraries

export_amarok_covers also requires several Python libraries and dependencies – argparse, ConfigObj, PIL, path.py and SQLAlchemy. Unfortunately, the script creator’s suggested method for installing the dependencies as follows:

sudo easy_install PIL ConfigObj path.py SQLAlchemy argparse

didn’t work for me, so I manually downloaded each library, then installed with easy_install:

wget http://cheeseshop.python.org/packages/source/a/argparse/argparse-0.8.0.zip http://jaist.dl.sourceforge.net/sourceforge/configobj/configobj-4.5.3.zip http://effbot.org/downloads/Imaging-1.1.6.tar.gz http://pypi.python.org/packages/source/p/path.py/path-2.2.zip#md5=941660081788282887f652510d80e64e http://pypi.python.org/packages/source/S/SQLAlchemy/SQLAlchemy-0.5.2.tar.gz#md5=616893cbfb7b04a4f0ca9587bded3a1c
sudo easy_install argparse-0.8.0.zip configobj-4.5.3.zip Imaging-1.1.6.tar.gz path-2.2.zip SQLAlchemy-0.5.2.tar.gz

Final Tweaks

The first time I ran the script, it threw some errors at me, regarding the script’s MySQL connection variables mapping method, which actually turned out to be a problem with my amarokrc file, in which for some reason, some MySQL connection parameters were missing. To remedy this, I edited the file:

gedit ~/.kde/share/config/amarokrc

and added to the [MySQL] section the following lines:

MySqlHost=localhost
MySqlPort=3306
MySqlDbName=AMAROK_DB_NAME

Running export_amarok_covers

Once everything is set up, it’s just a case of making the script executable and running it, so from a Terminal, run:

cd ~/Desktop
chmod +x export_amarok_covers
./export_amarok_covers

There are also a number of options, listed on the script creator’s site, which allow you to specify the name of the output file, create Desktop Entries, and so on.

When the script has finished running (it’s very fast), you should find each album art image within the location of the respective album.

Now I need to work on batch importing the covers to the MP3’s ID3 tags!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I was thinking a while back “wouldn’t it be cool if there was a desktop reporting tool for Google Analytics – I could just run it, and it’d sit there quietly in the background waiting from me to press Alt+Tab”, when a friend pointed me to an interesting Bundle on YouBundle – “Best Adobe AIR Desktop Applications“. Sat amongst the application list, was the “Google Analytics Reporting Suite” – Just what I need! The only thing is, I didn’t have Adobe AIR installed… So, here’s how I went about getting it installed…

Installing Adobe AIR 1.5 Linux

64 Bit Users Note: Adobe AIR is not yet available as a 64 Bit application, so you’ll need to install 32 bit libraries first. If you haven’t got them already, in a Terminal, run:

sudo apt-get install ia32-libs

Adobe AIR 1.5 is available for Linux. The binary can be downloaded from http://get.adobe.com/air (it auto detects your system). Once the file had downloaded to my desktop, I opened a Terminal (Applications -> Accessories -> Terminal), made the AdobeAIRInstaller.bin executable, and ran the file:

cd ~/Desktop
chmod +x AdobeAIRInstaller.bin
sudo ./AdobeAIRInstaller.bin

This fires up the Adobe AIR installer GUI, and it’s installed in a couple of clicks. It needs to be run with sudo, since it installs into /opt. The uninstaller, by the way, is located in the Applications -> Accessories menu.

Additional 64 Bit step

I didn’t actually run this, as everything seems to run fine, but in a Terminal, run:

sudo cp /usr/lib/libadobecertstore.so /usr/lib32

Installing Google Analytics Reporting Suite

This part should be easy – it should just be a case of visiting http://www.adobe.com/cfusion/exchange/index.cfm?event=extensionDetail&loc=en_us&extid=1282521 and clicking on “Install”. However, for some strange reason, the page wouldn’t detect my flash plugin properly – even though I have the latest 64 Bit version (albeit Alpha) installed from Adobe – so instead of the install box, I just had a box telling me to install Flash. No worries – with some sifting through the page’s HTML source code, I found the flash installation application just points to http://www.aboutnico.be/updates/gas32.air, so I just entered that into the browser, and when Firefox prompted, selected “Open with Adobe AIR Application Installer” – this downloads the file, and begins the installation.

I went through the motions – enter Admin password, choose location to install etc. and that was it. Once installed, it’s launched from Applications -> Accessories -> Analytics Reporting Suite. No more pesky logging in (except, of course, for the initial account setup).

A Note about TweetDeck

Many people seem to be having problems getting TweetDeck to work, so after some digging around (see comments below) I found a solution on http://beegod.org/tweetdeck-on-hardy-heron-64bit. It basically involves using getlibs to resolve dependency issues with the libgnome.keyring.so 32 bit library. In a Terminal, run:

wget http://www.boundlesssupremacy.com/Cappy/getlibs/getlibs-all.deb
sudo dpkg -i getlibs-all.deb
sudo getlibs -l libgnome-keyring.so.0.1.1

Postscript: Some people may be wondering why the image at the head of the post says “Adobe AIR for Linux beta”. Well, I originally wrote this post some time ago in November 2008, using Adobe AIR v1.1 Beta, but the whole setup was a little buggy – i.e. I couldn’t configure any account information in the Google Analytics application. It seemed a little pointless publishing a post when the software didn’t work, so I waited until everything did work – i.e. Adobe AIR v1.5. I just can’t be bothered to find another image, upload it etc…

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Update 05/02/09: Sun have actually released the update – no more beta -  so I’ve modified “Install Java JRE 1.6.0 (Update x) in Linux as the Default Java Runtime, including Firefox Browser Plugin” to reflect this (even the title has changed – although the URL remains the same!). The following tutorial remains for reference etc.

Back in January 2003, a bug was submitted to Sun pointing out that there is no 64 Bit Browser plugin support for JRE. Almost 6 years later, the issue seems to have been addressed: with the latest Beta release of JRE6 Update 12, Sun have finally developed and included the required Plugin to run 64 Bit Java, in a 64 Bit Web Browser on a 64 Bit OS. So, I decided to give it a try, and see what’s what. Since this is a Beta release (currently b3), and also deals specifically with 64 Bit, I’m keeping this post separate from my main HowTo on installing JRE: Install Java JRE 1.6.0 (Update x) on Hardy as the Default Java Runtime, which will be updated to include the new information when JRE6 u12 Final is released – hopefully sometime early this year (2009).

The first step is to download the installation file, jre-6u12-ea-bin-b03-linux-amd64-22_dec_2008.bin, which as usual was saved to my cluttered desktop. I have previous versions of JRE installed in /opt/java, but the directoty can be created as follows, if it doesn’t already exist:

sudo mkdir /opt/java

Once the installation file had downloaded, I moved it to the /opt/java directory, made it executable, and ran the setup:

cd /opt/java
sudo mv ~/Desktop/jre-6u12-ea-bin-b03-linux-amd64-22_dec_2008.bin /opt/java
sudo chmod 755 jre-6u12-ea-bin-b03-linux-amd64-22_dec_2008.bin
sudo ./jre-6u12-ea-bin-b03-linux-amd64-22_dec_2008.bin

After reading and agreeing to the Licensing terms, the executable extracts all the relevant files into a subdirectory: jre1.6.0_12

Setting JRE6 u12 as the Default Java Runtime

To install JRE6 u12 as the default Java for the system, simply run the following two commands:

sudo update-alternatives --install "/usr/bin/java" "java" "/opt/java/jre1.6.0_12/bin/java" 1
sudo update-alternatives --set java /opt/java/jre1.6.0_12/bin/java

Following the execution of both commands, there should be output along the lines of:

Using '/opt/java/jre1.6.0_12/bin/java' to provide 'java'.

Installing the Browser Plugin

The part I’m really interested in for the moment, is getting the 64 Bit JRE Browser Plugin installed, which thankfully is very easy. As with most Firefox plugins, they can be installed in ~/.mozilla/plugins – if it doesn’t exist, it can be created:

mkdir ~/.mozilla/plugins

It may also be necessary to uninstall any previous Java installations, such as IcedTea etc.:

sudo apt-get remove icedtea-gcjwebplugin

The Plugin can be installed by either copying the file:

cp /opt/java/jre1.6.0_12/lib/amd64/libnpjp2.so ~/.mozilla/plugins/

or by creating a symbolic link to the file (the best option, since it allows updating to the final release without recopying the file etc.)

ln -s /opt/java/jre1.6.0_12/lib/amd64/libnpjp2.so ~/.mozilla/plugins/

Once installed, restart Firefox. There are two methods to see if the Plugin is installed – navigate to about:plugins

or to the Java Tester Page

Looks good so far – I can finally upload photos to Facebook using the Java Applet!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Getting JRE set up and Ready (Optional)

If you’d like to set up 64 Bit (or 32 Bit) JRE to run Eclipse, follow these instructions.

Installing the Base: Eclipse 3.4 (Ganymede) JEE

First, I downloaded the 64 Bit version of Eclipse IDE for Java EE Developers to my desktop (32 Bit version here). Once downloaded, I extracted the archive, then moved the files to /opt:

cd ~/Desktop
tar -zxvf eclipse-jee-ganymede-SR1-linux-gtk-x86_64.tar.gz
sudo mv eclipse /opt

For 32 Bit:

cd ~/Desktop
tar -zxvf eclipse-jee-ganymede-SR1-linux-gtk.tar.gz
sudo mv eclipse /opt

Installing PDT 2

Simple so far. Once moved (installed), I ran Eclipse for the first time from the command line:

cd /opt/eclipse
./eclipse

and selected a workspace within my home directory once prompted. From here, installing PDT 2 is an easy task – adding two sites to the Update Manager (far easier in Ganymede than Europa), and letting Eclipse to the rest. Once Eclipse had started, I went to Help -> Software Updates. The Software Updates and Add-ons window appeared, and I navigated to the Available Software tab. From there, I clicked the “Manage Sites” button, followed by “Add” once the Site Manager appeared. The only additional prerequisite to install for PDT is the Dynamic Languages Toolkit, or DLTK. So, I added:

http://download.eclipse.org/technology/dltk/updates-dev/1.0/

in the Dialog, and clicked OK. I then needed to add the PDT update site, so clicked add, and pasted:

http://download.eclipse.org/tools/pdt/updates/2.0/interim/

Click OK to close the Available Sites Manager. The rest is just as easy – two new sites should appear in the Available Software sites list. So, I expanded the DLTK site (the small triangle to the left of the site name), then the Dynamic Languages Toolkit option, and checked “Dynamic Languages Toolkit – Core Frameworks (Incubation)”, from the top of the list. Finally, I repeated the process with the PDT Update site – expanded PDT Update Site -> PDT SDK 2.0.0 and checked “PDT Runtime Feature” from the list. That’s it. Click Install and follow the prompts.

Once installed, Eclipse recommends restarting the application. Accept, restart, and enjoy a shiny new PHP IDE, with PDT 2.

Setting Up the Environment

Once Eclipse Ganymede has reloaded, click on the Workspace icon to open the IDE workspace for the first time. The default Perspective is JEE. To change this, go to Window -> Open Perspective -> Other, then scroll down and select PHP. Other Views, relating to other plugins can be inserted into this perspective, and the perspective saved for future use. Personally, I like to add the SQL Development views, and MyLin, for live access to Bugzilla (Window -> Sow View -> Other).

A new PHP Project can be started by right clicking in Project Explorer (left window pane), and selecting New PHP Project (“Other” may need selecting on the first run, followed by navigating to and selecting PHP Project from the list).

That’s it. Far easier than previous versions, and much less effort required in the process! We like that.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.