• Adobe Flash Player 9.0.124 or higher
• GTK+ 2.12 or higher
• GLib 2.16 or higher
• LIRC 0.8.2 or higher (required for remote control functionality)

[Warning!  Old Article that was moved!]

sudo gedit /etc/apt/sources.list

Add the following line to the end of your sources list.  This will add the reposititory to install KDE.  Where [your version] is please replace with the appropriate name:  jaunty, intrepid, hard, et cetera.

deb http://ppa.launchpad.net/project-neon/ubuntu [your version] main

Add the key to access the repo

gpg --keyserver keyserver.ubuntu.com --recv-keys 493B3065 && gpg --export -a 493B3065 | sudo apt-key add -

Update your packages...


Then install KDE!

Whenever uncompressing the compressed, always, I mean always, give the compressed file its own directory (ie, folder).  Why?  Some tarballs when unleashed explode out so my files, that directory is covered in shrapnel.  You effectively made yourself cannon fodder.  So please don't. 

Its not just about Classical versus Neoclassical.  This is about installing packages designated for i386 versus x64 versus PPC versus x86.  First, what does all that mean?  Second, why does it matter?

Architecture refers to the chipset/processor in your system as well as the operating system installed.  For example, I can install 32 bit (x86) Linux on an AMD Athlon 64 bit processor.  Likewise, I can install the 64 bit (x64 or x86-64) OS on a 64 bit processor.  However, I cannot install x64 on 32 bit.  I also cannot install an x86 or x64 OS on a PPC system (think old school Mac).  Similarily, I cannot install the PPC version of an OS on an x86 or x64 bit system.  Wow.  Did you keep up with that?  Heh.  That's the confusing part, I think.

Why does it all matter?  Here's your first scenario:  I am running a 32 bit system.  I download the 64 bit version of a package I want.  The 64 bit package will not install on a 32 bit system.  However, I can install 32 bit packages on 64 bit systems with some finnagling. 

So with compatibility in mind, I'm going to through one more issue at you: optimization.  Think of this as putting the right gas in your car.  No sense in using Premium if your car does not require it.  Some distros will split their distros in a variety of architectures such as i386, i486, i586, and i686.  In the case of such division, looking for packages labelled as such will boost your performance.  If you install a package built for i686 on an i486 system, it will indeed work.  Unfortunately, you lose any performance advantage that the distro and matched packages would have brought you. 

Finally, some systems use either alldeb or noarch packages to demontrate that there is no specialization or optimization involved.  These are fine for all systems. 

Most Linux distros utilize either RPM or DEB packages to install files (much akin to Window's EXE files in the grand scheme).  Stick with those files (or whatever package your particular distro uses). 

What do packages do in the first place?  They work with your Package Manager to track all the installed files on your system.  However, the Package Manager only tracks what was installed through it.  This is where the issue with source files comes into play.

Source files require the user (probably you, just guessing) to compile and install them.  Its a pain anyway.  So don't do it.  But if you need a more compelling reason, here's why:  Once that source (src) file is installed, you are the only person to know that it got installed by such crude methods.  Your Package Manager will be helpless to remove that application once you decide you are done with it.  Then you are left with leftover files that you may not need.

Still not good enough?  What about dependencies?  Your Package Manager also tracks and installs every little library or file that is necessary to make your new Soduko game work.

Summary:  Don't use source files.  Please.

LinuxApp

LinuxAppFinder has a piece on how to rip your DVD movies to MPEG4 with k9copy. The author claims that k9copy ripped the movies with less errors and had better features than dvd::rip. Now if I could just find a good way to burn my movies back to DVD. Any suggestions?

LinuxAppFinder is also great if you're just looking for an alternative to a Windows or Mac program.

Finder has a piece on how to rip your DVD movies to MPEG4 with k9copy. The author claims that k9copy ripped the movies with less errors and had better features than dvd::rip. Now if I could just find a good way to burn my movies back to DVD. Any suggestions?

LinuxAppFinder is also great if you're just looking for an alternative to a Windows or Mac program.

HandBrake is a handy open source free application for converting video from DVD to MPEG.  Part of what makes this program great is that it will handle so called encrypted movies (provided they are utilizing CSS).  Plus, it works on Linux, Mac, and Windows.  I won't go into great detail about this project, but its worth a try.

If someone has some free time, please convert this into a DEB and get it into Ubuntu/Debian repos.  Its promising but useless for a lot of users if its stuck as a Tarball.

As I just upgraded to Ubuntu 9.04 Jaunty (still alpha actually but working nicely), its time to make sure all my hardware works.  Traditionally my Canon MultiPASS MP390 does not work completely (the scanner is completely unsupported) but the printer component usually works with a little finagling.  So here is my journey towards printing freedom.  Hopefully this will work well for others as well.

Start out with The Linux Foundation's OpenPrinting database (screenshot). 

Select the Printer list.  From here you can choose the make and model of the printer (screenshot).  Once found, select the printer and click SHOW.

This will take you through the steps to making backup copies of purchased movies on Linux.  Windows has several commercial options available but Linux is of course, all free and open source.  There are several options on Linux but today I'm looking at two:  HandBrake and Shrinkta.

HandBrake (v 0.9.2) is handy for converting the movie into different file formats (MP4, MKV, AVI, OGM).  This allows you to take the movie along on an iPod or just keep them all your laptop while you travel.  The downside to HandBrake is copying to another disc.  HandBrake's default setting is for DVD and will create a "video_TS" folder when ripping.  I just wish it would be also burn the disc.  You can download HandBrake direct from their website www.handbrake.fr but it is a tarball for Linux.  Mac and Windows installers available too.   I will soon have a DEB file available for download.  Keep in mind you need to also install Mono to meet the dependencies.  In the short time, Linux Crypt has the how to for installing HandBrake.  The easier way:  download the two deb files and open them once they're downloaded on your system.  Skip the terminal business that's mentioned.

The other option is Shrinkta.  This app is vastly simpler than HandBrake. Shrinkta never did work for me though.  It had trouble recognizing my DVD drive.  When it finally did, it locked up and I was done with it.  If it works for someone, it looks promising.  A DEB file is availlable at GetDeb.  Oddly, this program is also called DVD Movie Backup at some sites and it shows up that way once its installed.

Note!  All my work was done on Ubuntu 8.04 Hary Heron.  I cannot say what will happen on an older system.