With the prevalence of software available for many distros, why would anyone want to compile software from source? Compiling allows you to custom-fit a program to your particular hardware configuration and CPU architecture, which is useful if a program has no binary that is compatible with your processor. However, this is seldom a problem these days, since most computers now use 32 or 64-bit x86 processors. In the past, Linux enthusiasts often compiled programs from source to wring the greatest possible performance out of their hardware. More recently, this has mostly become a non-issue due to the increases made in computing speed; while compiling may offer a slight performance increase, it is not enough to really make a difference.

Although the introduction of package management on most distros, less diversity in CPU architecture among the user base, and massive increases in hardware speed have largely reduced or eliminated the need to compile software yourself, there are still a few instances where you would have to do so. Although the various official and unofficial software repositories for Ubuntu and other distros include most of the tools that the average user would need for any given purpose, the repositories are not completely comprehensive.Old packages sometimes get dropped and updated versions are often slow to be added. It may also take a release cycle or more for brand-new programs to be included.

While Ubuntu and Debian have “backports” repositories that have fairly new packages in them, many other distros do not have such a resource. For large projects with large community support, the developer may offer nightly builds, but this is not the case for most projects. The only reliable way to get bleeding-edge software (stability issues aside) is to either find a repository that has it or download the source code from the developer and build it yourself.

Read on to get started!

These days, most people have at least one computer and a large collection of media files. The conventional practice for most people has always been to have redundant copies of their media collection on their various computers. While this system technically works, it is highly inefficient and creates the unnecessary task of keeping the media collection on each computer synchronized and up-to-date with the others. A far better solution is to keep all the media on one computer and stream it as needed to the other machines over the network.

Streaming technology has been around for over a decade and is something that most people are at least a little familiar with. (Youtube uses streaming flash-based video to work)  In the past, playing large files over the internet was usually pointless due to the fact that the software of the time  required the whole file to download (often on slow connections) before the media could be played. With streaming media, the remainder of a file is fetched as the first part it is being played, so there is no need to wait to get the whole thing before watching it. The video quality on early streaming media was often quite bad, (a trade-off between quality and speed was necessary when most people were stuck on dial-up) but with the near-ubiquitous availability of broadband in most urban and suburb areas today, high-quality streaming media has finally become practical.

We have assembled this guide to help you set up a cross-platform media streaming service using a Linux computer as a server. With our guide, you will be able to stream media to any other computer you own. Other guides on the subject discuss how to set up a Samba-based solution, but we feel that our solution is simpler and easier since you only have to install and configure one program instead of several. For this purpose, we use GNUMP3d. GNUMP3d  is a program that makes media available through a web-based interface. Instead of using the Samba protocol, GNUMP3d uses ordinary HTTP to get the job done.

Read on to get started!

Today, we live in a world of rapidly diminishing privacy. If you use your employer's email system, it is possible that every message you send or receive is logged and intercepted without your knowledge. This may have unintended or even disastrous consequences if an intercepted email message contains sensitive personal information. Unless your email goes through Secure Socket Layer (SSL) protected connections, your email is vulnerable to what is known in the IT security field as man-in-the-middle attacks, where an attacker can intercept your message as it flies to its intended recipient.

Email is sent in a format that is easily readable if an attacker can grab and reconstruct enough pieces (packets) from the data transmission with packet sniffing software. Technologies like deep packet inspection make it theoretically possible that any given message that goes over the internet can be sniffed and read by third parties who have the right software and know-how. (the feds, your ISP, etc.) While no one may have a real reason to spy on you, relying solely on security through obscurity has always been a poor policy to live by. Because of this, encryption is the only real option you can trust. We teach you how to put your emails in a lockbox before sending them off to their destinations.