Getting access to gmail accounts of the deceased

Do you have a gmail address ? And do you store sensitive information in your gmail account which you have received from your contacts ? Then you (or rather people close to you such as your family) might be interested in knowing the ways in which someone can gain access to your account in the event of your demise.

You have to follow a number of procedures to eventually gain access to someones gmail account. This article explains what it takes to make google reveal the password of a gmail account not your own.

While this is not strictly related to Linux, I am sure you will find this information useful as I have because, I have an email address at gmail.com.

QEMU-Puppy - A portable personal computer on a USB stick

A few months back, I bought a 4 GB Kingston USB memory stick. It cost me around 1800 Indian Rupees (In US dollars it comes to just over $45). My idea was to use it partly as a data storage where I could keep files as backup and to use a part of the USB stick to install Linux.

The USB stick initially had only a single FAT 32 partition. So I repartitioned the USB stick to two 2 GB partitions each, both having FAT 32 file system. And in the first partition, I decided to install Linux. I went through the process and copied the distribution of my choice to my USB stick partition and even made it bootable using syslinux - which is a boot loader for Linux operating system. But as luck would have it, my computer refused to boot from the USB stick complaining there was no boot loader on the USB stick.

Later I came to know that syslinux has a limitation of working only if the partition is less than 1GB size and my USB stick had a partition of 2 GB. I didn't get the time to go back and try it out again. Perhaps I will try it some time soon on a 1 GB partition.

Today I came across this quite exhaustive but very informative article titled - "QEMU-Puppy - A Personal Portable Computer" written by Erik Veenstra where he explains how to turn your USB stick into a personal portable computer. He uses Puppy Linux (A very good minimalistic Linux distribution) and QEMU for the same. Erik walks one through the installation of QEMU and Puppy, to booting, configuration of various parameters, some tips and tricks that will save your time and a bit of Puppy Linux internals. All in all a very interesting article and a project worth trying out.

LINA - Truly portable Linux applications

A truly portable application is one which can be run on multiple operating systems spanning diverse architectures without recompilation of code. One language which creates truly portable applications is Sun Microsystem's Java language. Programs created using Java can be run under any operating system - be it Mac OSX, Windows, Linux, OS/2 and so on. This is made possible because programs compiled using Java are not binaries in the original sense. When you compile a Java program, you get byte interpreted code. And it is the duty of the Java virtual machine which is installed in the parent OS to interpret the code to machine language which the OS and the architecture can understand.

Now there has been a new development for Linux. A startup company in Alameda, California has developed a technology called LINA (Not an acronym) which allows one to compile Linux applications to make them run in any operating system - be it Windows, Linux or Mac OSX. The idea is to have a virtual machine in similar lines of Java virtual machine which will be released as native builds for the respective operating systems. Then developers and independent software vendors can build Linux applications on top of LINA that run on all operating systems with native look and feel.

The company plans to dual license the technology, with GPL ver 2 for non-commercial uses and a separate license for commercial uses.

Salient features of LINA

• Applications written for LINA are distributed as Linux executables guaranteed to run on all machines, Linux and otherwise. So you can have say, one Firefox build which runs flawlessly in Windows, Linux, Mac OSX or any other operating system.
• Portable LINA applications enable users at home and in the enterprise to use Open Source applications on their existing operating systems.
• With LINA installed, programs written for Linux will run securely, regardless of changes made to the underlying operating system.
• Developers can write the code once and run their applications anywhere.
  

You can get an idea of running LINA applications by viewing this screencast which demonstrates how a Linux native build of links web browser packaged using LINA is run in Windows.The company has also released a white paper (PDF) describing the LINA technology. While some might see LINA as similar to what Sun Microsystems has accomplished with Java language, it is notably different. In the case of Java, it is required that programmers sit down and start developing programs using this language. But as far as LINA is concerned, the applications are already there in the form of 10s of 1000s of open source and Free Software programs for Linux. And it is only a matter of re-compiling the source of these programs to run using LINA virtual machine.

While many would consider this new project quite exiting (who wouldn't want a truly portable copy of their favorite Linux application, right?), there has been a somewhat similar project in existence for some time now which goes by the name Cooperative Linux. Short named as coLinux, it is a port of the Linux kernel that allows it to run cooperatively alongside another operating system on a single machine.

TrueCrypt Tutorial: Truly Portable Data Encryption

TrueCrypt is one of the many disk encryption tools available in Linux and other Unices. Some of the features of truecrypt are as follows (and I quote):

• Creates a virtual encrypted disk within a file and mounts it as a real disk.
• Encrypts an entire hard disk partition or a storage device such as USB flash drive.
• Encryption is automatic, real-time (on-the-fly) and transparent.
• Provides two levels of plausible deniability, in case an adversary forces you to reveal the password:
  
  1. Hidden volume (steganography).
  2. No TrueCrypt volume can be identified (volumes cannot be distinguished from random data).
• Encryption algorithms: AES-256, Serpent, and Twofish. Mode of operation: LRW.
  

Lipiec at Polishlinux.org has written a very good tutorial which explains how to setup and use truecrypt in Linux. He explains right from the start which is - download the code, compile, and install it to creating encryption volumes. Just so you know, truecrypt has been made available in deb and rpm formats as well. So if you are using one of the major Linux distributions such as Debian, Ubuntu or Fedora, you can skip the compilation from source step.

Truecrypt is available for Linux and Windows but the developers have provided a easy to use GUI only for Windows platform. Linux users are still made to depend on the command line to setup and manage encrypted volumes using truecrypt.

FFmpeg tutorial - Develop a video application in less than 1000 lines of code

FFmpeg is a library which can be used to build applications that record, convert and stream audio and video. It includes libavcodec, the leading audio/video codec library. FFmpeg is developed under Linux, but it can compiled under most operating systems, including Windows.

The FFmpeg toolkit consists of a number of programs them being :

• ffmpeg - which can be used to convert one video format to another. Say you want to convert a YouTube video in flv format to mpeg format, this tool will help you convert it.
• ffserver - This is a HTTP server which can be used to stream audio and video across the web.
• ffplay - is a simple media player based on SDL and on the FFmpeg libraries.
• libavcodec - a library containing all the FFmpeg audio/video encoders and decoders. Most codecs were developped from scratch to ensure best performances and high code reusability and ...
  
• libavformat - which is a library containing parsers and generators for all common audio/video formats.
  

I came across this excellent tutorial on Ffmpeg where the author demonstrates how to develop a video player in less than 1000 lines of code. Just so you know, one of the prerequisites of understanding the tutorial is some knowledge of the C language.

While on the subject of videos, you may also be interested in the different ways of creating screencasts in Linux.

Work productively without starting X server in Linux

When was the last time you logged into a console only mode in Linux ? By console only mode I mean in run level 2 or 3 where X server is not running? Obviously now-a-days you needn't resort to such a drastic step as the GUI applications have gotten richer and the end user has a variety of choices before him. More over, most Linux distributions boot into graphical X by default the very first time they are installed. I am willing to bet that in a couple of years time, the new users embracing Linux won't have any idea of what a console mode is unless somebody specifically tell them.

This was not the same till a few years back (go back to 8 years) when even the average user had to first deal with the console mode and learn to start X by running a command before he was put into a graphical environment. He had to learn the syntax of the XF86config file (it is now xorg.conf), learn to use a console editor and so on before he was able to enjoy the fruits of Linux in GUI mode.

On this note, if you are wondering how the heck then the people using Linux were productive, it seems there were a number of command line tools at ones disposal. They are still around (if one bothers to look). Luke at "Terminally Incoherent" blog has compiled a nice list of command line tools in an article titled "A day without X", where he lists console programs that help one to accomplish common tasks like sending and receiving emails, web browsing, viewing images and so on. Another blogger, K.Mandala has also compiled his own list of command line applications which you can read here.

Who knows, if you face a situation where your favorite uncle gifts you with a 486 machine loaded with a stripped down version of Linux as a birthday present, you can genuinely be happy (instead of just pretending) and assure him that you will put it to good use....

PC-BSD 1.3.4 Review

FreeBSD along with OpenBSD and NetBSD form the triumvirate of BSD operating systems. Traditionally these BSDs are server centric operating systems - ie. those which are tuned to be run on a server rather than to be used by the end user as a desktop. Still, with a bit of tweaking and configuration, all the three of them can be used as viable desktop operating systems.

PC-BSD is a direct descendant of FreeBSD. As the name indicates, PC-BSD is a BSD operating system which lays stress on its use as a Desktop catering to the end users. From the point of its inception, the USP (Unique Selling Point) of PC-BSD has been to make it as easy as possible to install, update and use software, at the same time bringing all the powerful security features and stability of the traditional BSDs. Over one year back, I had reviewed PC-BSD 1.00 and if you have read the review, you would have found that my initial impression of this operating system was very positive. In the succeeding months many changes have taken place for PC-BSD. For one, in October 2006 PC-BSD got acquired by iXsystems which is now in control of the project - though Kris Moore, the founder of PC-BSD is still its project leader and has the final say. Apart from the acquisition, the project has moved quite smoothly.

One of the main changes I can see for PC-BSD 1.3 when compared to ver 1.0 is the drastic enhancement of the graphical installer with a couple of additional options thrown in. For example, at the time of installation, there is an option to encrypt the swap partition, there are options to open or close most popular ports such as the port used by SSH and so on, a choice of enabling or disabling the firewall and with a few clicks you finish installing the OS.

Fig: PC-BSD desktop

The current version of PC-BSD is ver 1.3.4. Some time back, I had downloaded ver 1.3.0 of PC-BSD and had installed it on my machine. The PC-BSD team have made it possible to upgrade the OS to the most recent version - 1.3.4 by downloading and installing a couple of patch files. Thus I had to download and install just over 40 MB of patch files which are made available in PBI format, to upgrade PC-BSD from ver 1.3.0 to 1.3.4. As a matter of fact, you do not even have to download individual files yourself to upgrade the OS. There is a GUI tool called "PC-BSD Online Update" which can be accessed by navigating through KDE Menu -> Settings -> System Administration -> "PC-BSD Online Update", that can be configured to automatically detect if there are updates available and then download and install them for you.

Post Installation scenario

It is really remarkable that the installation of PC-BSD went without any glitch and all the peripherals were detected properly. Sound worked out of the box and in no time, I was face to face with the graphical login screen. PC-BSD is a KDE centric operating system and comes with the latest version of KDE ver 3.5.5 and many useful software installed by default.

Once I logged into PC-BSD, I navigated to the PBI resource web page which contain the latest versions of most popular software such as FireFox 2.0.0.3, OpenOffice.org and so on and started installing those software which I use on a regular basis. As far as PC-BSD is concerned, you do not have to worry about dependencies as each PBI is a stand alone package which contain all the necessary libraries needed to run the program. So FireFox PBI will contain not just the FireFox binary but also dependent libraries as well.

Fig: It is possible to schedule the update of the OS to install security patches.

The PBI (short for PC-BSD Installer) is a GUI installer that is similar to its Windows counterpart, and is coded using Qt. To install a software, just double click on the respective PBI and follow the instructions. You also have the option of cleanly uninstalling the software from within the PC-BSD software manager.

Fig: View and remove the installed PBIs

Essential housekeeping in PC-BSD

One of the first things you should do the first time you boot into PC-BSD is to update the ports and install them. PC-BSD uses the FreeBSD 6.1 ports. And when you install software using the ports, you are essentially installing FreeBSD software. But unlike FreeBSD where you have to dabble with command line to update and install the ports, in PC-BSD, you can do the same using the GUI front-end with the click of a button (See the image below).

Fig: Install ports with the click of a button

Next I had to install the multimedia codecs to enable PC-BSD to play audio and video files in proprietary media formats. As with all Open Source projects, PC-BSD also follows the principle of not shipping the proprietary codecs by default and requires that the end user install them by themselves if they want to. Here is the interesting part. To install the multimedia codecs, all I had to do was to download and install the requisite PBI file from the PBI online repository. And viola!!, I was able to not only play wmv and quick time files but also watch encrypted DVD movies as well.

Fig: Kaffene media player detects all the codecs.

I have an Nvidia graphics card and I wanted PC-BSD to harness the full potential of the graphics card. Usually you can get along very well with the Nvidia open source driver but if you want to use OpenGL programs for instance, you need to install the proprietary driver. In the PBI repository, you will find a number of builds of Nvidia proprietary drivers for PC-BSD and you can choose the best package which works for you.

I found enabling Flash to be a little tricky affair. Mainly because Adobe has not yet released Flash Player ver 9.0 for BSDs. And the native build of Flash player for BSDs is still at ver 7.0. While you can very well install this version of flash player, many flash enabled websites now a days require you to have version 8.0 or above to view them - a big handicap for BSD users. One work around you have for PC-BSD is to install the Linux version of FireFox web browser. You heard me right. It is possible to install most Linux software and run them without any modification in PC-BSD. This is made possible because PC-BSD has a Linux compatible module installed.

I installed the Linux version of the latest build of FireFox from the PBI online repository as well as the Flash player ver 9.0 from here. And I was able to view flash websites without any problem. Of course I encountered a minor glitch in that each time I open two flash based websites simultaneously, Linux version of FireFox crashes. But by and large I was able to manage as long as I had only one flash website open at any given time.

I also downloaded and installed Sun's JDK 1.5 from the PBI online repository.

Is PC-BSD a FreeBSD clone ?

At first glance, one might be tempted to pass off PC-BSD as a clone of FreeBSD with some frills thrown in, as PC-BSD uses the FreeBSD ports. And it is easy to think that if you are installing software using ports, you are essentially getting FreeBSD software. But on close scrutiny, I was able to find notable differences. Some of them are as follows :

• A GUI installer which eases the installation process.
• Use of PBIs to install many software.
• Incorporating OpenBSD's robust and powerful PF firewall instead of the firewall bundled with FreeBSD.
• Many GUI front-ends which aid package management.
• Easily start/stop and enable/disable services via its equivalent GUI.
• Use of blacklist script to automatically ban IP addresses of machines of potential crackers who try to hack into your machine.
  

Suggestions for further improvement of PC-BSD

1. The three BSDs namely FreeBSD, OpenBSD and NetBSD have their own independent ports. PC-BSD team could also start maintaining its own independent ports system instead of depending on the FreeBSD ports. One disadvantage of depending on FreeBSD ports is that you have to sometimes wait a long time before the software gets updated in the ports.
   
   Take for instance GnuCash finance software. It is not easy to create a standalone PBI of GnuCash as it has to satisfy a lot of dependencies. And as of now the FreeBSD ports have the older version (1.8) of GnuCash which is markedly different from the latest version of ver 2.0 especially in the file format which the respective versions use to save the data. And the PC-BSD team has to wait until the GnuCash port has been updated to the latest version by the FreeBSD port maintainers. Truth be told, there is a GnuCash 2.0 place holder in the ports I downloaded in PC-BSD but when I give the command :
   

   # make install clean
   
   ===>   gnucash-2.0.5_3 depends on package: guile>=1.6.8_2 - not found
   ===>   Found guile-1.6.8_1, but you need to upgrade to guile>=1.6.8_2.
   *** Error code 1
   
   Stop in /usr/ports/finance/gnucash.
   *** Error code 1
   

   ... it complains that guile package is an older version and GnuCash requires a newer version of the same. These snags could be done away with if PC-BSD maintains its own ports with periodic selective syncing with FreeBSD ports.


2. When a user enters a root password to do system administration tasks using GUI, PC-BSD should offer to remember the root password so that the user does not have to enter it the next time he want to run a program in super user mode. Many Linux distributions such as Debian and Fedora have this feature. At present, if I want to install say 10 PBI's I have to enter the root password 10 times - ie. each time I execute the PBI, it asks for root password which gets really tedious. KDE dialog has a check box which offers to "keep the password" but it doesn't seem to have any effect.
   
   
3. The PBI should have an option to install software system wide or on a per user basis. This suggestion might seem strange but in a multi-user environment, it is not possible to hand over the root password to every one. And if a user wants to try out a software by downloading the PBI, he should be allowed to install it in his home directory if he cannot enter the root password.
   
   
4. The PBI should also support execution from the command line. This is not a must have feature but it can be convenient to execute and install a PBI package in certain situations where you have booted into console mode.
   
   
5. It would be nice to have a GUI front-end which allows a lay person to write custom firewall rules for PF.
   

Epilogue

PC-BSD is turning out to be an excellent alternative to other popular Desktop OSes. After testing and using PC-BSD for some time now, I can't but admire the sheer amount of work that is put into creating, developing and molding an OS for the lay person albeit with a strong slant towards FreeBSD. The fact that PC-BSD is able to accomplish all the tasks expected by an end user - be it using the Internet for communication, listening to music, watching movies or using it for recreation purposes holds it in good stead as a viable Desktop OS.