Reehan's Blog

A number of you have reported issues with the T-shirt Design Contest poll. We have reviewed these reports in depth and want to thank you, the community, for bringing them to our attention.

Indeed, the T-shirt voting poll has been demonstrating some irregularities. To be specific: we've received multiple votes from the same IP addresses during the same 24-hour period. As we stated when we launched the poll, voters should only be able to vote once per day. This has inflated the results for some of the designs, and we can no longer trust the ultimate poll results.

Because the winning design will be the basis for this year's LinuxCon attendee T-shirt and honored as the 20th Anniversary of Linux design, we are restricted by a timeline to get the design to print in time for the special event. As a result, we have appointed a panel of people representing Linux.com, LinuxCon and the overall Linux community to choose the winner from among our six finalists this year. This is a respected and trusted group of community members who we believe together will honor the designers and this year's important milestones with a smart, thoughtful choice. This format is similar to the judging we conduct for the annual Linux Foundation Video Contest.

Because of this change and to express our sincere thanks to each designer for participating in the 20th Anniversary of Linux T-shirt Design contest, we want to do something to recognize each of our finalists. So this year, we will have the five runner-ups each printed on one, limited edition T-shirt, framed and put on display in a special gallery at LinuxCon. Afterwards, we will mail the framed T-shirts to their respective designers. As reported, the winning design will be the basis for the LinuxCon attendee T-shirt and will be available to purchase in the Linux.com Store. Though, the winner will also receive one of their T-shirts, framed, as well.

Our T-shirt Design Contest Judging Panel is:

Joe "Zonker" Brockmeier, managing editor, Linux.com
Angela Brown, Events Director, The Linux Foundation
Matthew Fillpot, 2011 Linux.com Guru and Linux.com Moderator
Jon "maddog" Hall, FOSS veteran and advocate, LinuxCon keynoter

The panel will review the designs through June 22, 2011, and the winner will be notified and announced shortly thereafter.

We are sorry for this divergence from our original voting system for this year's contest and thank the community again for bringing the issues to our attention. Our aim is to be transparent and fair, and we look forward to honoring all of this year's finalists in the weeks and months ahead. 

View the original article here

For those who are curious about the "patent reform" bill working its way through the U.S. Congress, Groklaw has a critical summary of the changes. "And where are most of those 'fixes' aimed? At addressing the reexamination of patents that contain claims that likely should have never been allowed. Doesn't it make more sense to focus and invest on achieving thorough examinations in the first place? Well, yes, it does, but there are serious interests out there that really don't want that to happen. Why? Because regardless of whether a claim is ultimately found valid, a patent has value by its mere existence because of the high cost of patent litigation. This legislation is not going to fix that problem."

View the original article here

The Perl developers have updated 5.14, the current stable development branch, and released a maintenance update for the previous stable branch 5.12, while recommending users upgrade to 5.14 when convenient

View the original article here

This document describes how to integrate Postfix/Dovecot with Microsoft Active Directory on CentOS 5.x, and you can manage mail users in Microsoft Active Directory. You will learn how to enable Postfix to look up email addresses in Active Directory and how to enable Dovecot to authenticate against Microsoft Active Directory.

View the original article here

Red Hat has announced the availability of version 2.0 of its Enterprise MRG ("messaging, realtime, and grid") distribution. It features an update to RHEL 6.1, a number of claimed performance improvements, and a bunch of buzzword-compliant cloud features. "Enterprise MRG Messaging 2.0 services as a foundational layer of infrastructure in Red Hat's OpenShift Platform-as-a-Service (PaaS) solution, introduced in May 2011. With Enterprise MRG 2.0, OpenShift gains a reliable, scalable mechanism for transferring data in the cloud, as well as the interoperability of the AMQP open standard."

View the original article here

Adlink announced the availability of a $672 fanless industrial computer, equipped with a dual-core, 1.66GHz Intel Atom D510 processor and said to be resistant to extreme temperatures, shock, and vibration. The MXE-3000 features SATA and CompactFlash storage, dual display support, PCI Express and 3G SIM expansion, three gigabit Ethernet ports,...

Adlink announced the availability of a $672 fanless industrial computer, equipped with a dual-core, 1.66GHz Intel Atom D510 processor and said to be resistant to extreme temperatures, shock, and vibration. The MXE-3000 features SATA and CompactFlash storage, dual display support, PCI Express and 3G SIM expansion, three gigabit Ethernet ports, six USB 2.0 ports, and four serial ports, says the company....

View the original article here

A second release candidate means that Samba 3.6 could be weeks or months away. 3.6.0 will see the first full featured implementation of SMB2 but it will be turned off by default...

A second release candidate means that Samba 3.6 could be weeks or months away. 3.6.0 will see the first full featured implementation of SMB2 but it will be turned off by default

View the original article here

IHS iSuppli published the results of a teardown of the 3G version of Samsung's Chrome OS-based Series 5 Chromebook -- which began shpping today for $500 -- and estimates the solidly-built notebook cost $334.32 to build. Meanwhile, an eWEEK review of the Wi-Fi only Series 5 was similarly impressed with...

IHS iSuppli published the results of a teardown of the 3G version of Samsung's Chrome OS-based Series 5 Chromebook -- which began shpping today for $500 -- and estimates the solidly-built notebook cost $334.32 to build. Meanwhile, an eWEEK review of the Wi-Fi only Series 5 was similarly impressed with the hardware, but questioned whether Chrome OS would find many takers....

View the original article here

The laptops, which feature Google's Chrome OS, can now be preordered via Best Buy and Amazon, Google says. Chrome OS itself, meanwhile, remains a work in progress.

The laptops, which feature Google's Chrome OS, can now be preordered via Best Buy and Amazon, Google says. Chrome OS itself, meanwhile, remains a work in progress.

View the original article here

Continuing to ensure that Linux benchmarks on the latest AMD Radeon HD graphics processors are available, the kind people at Sapphire have sent over another Radeon HD 6000 series graphics card. After previously reviewing the Sapphire Radeon HD 6570 and Sapphire Radeon HD 6870, up now is the Sapphire Radeon HD 6770. The Radeon HD 6770 (and HD 6750) up until recently was just offered to OEM builders, but now Sapphire has begun selling various products with these graphics processors, which end up being re-branded Radeon HD 5770/5750 "Juniper" graphics processors.

View the original article here

Version 2.1 of the SeaMonkey browser (and more) is out. "Building on the same Mozilla platform as Firefox 4, it delivers the latest developments in web technologies such as HTML5, hardware acceleration and improved JavaScript speed." Also included are cross-device synchronization, "personas," a new unified personal data manager, better plugin...

Version 2.1 of the SeaMonkey browser (and more) is out. "Building on the same Mozilla platform as Firefox 4, it delivers the latest developments in web technologies such as HTML5, hardware acceleration and improved JavaScript speed." Also included are cross-device synchronization, "personas," a new unified personal data manager, better plugin handling, and more; see the release notes for details.

View the original article here

A newly unveiled startup says it has devised a CMOS platform that can cut the active power consumption of & a wide range of integrated circuit products& by half, and leakage power consumption by up to five times. SuVolta says its & PowerShrink& platform has already been licensed by Fujitsu, which will offer it in 65nm products in 2012....

View the original article here

Twice a year, the Top500 Project publishes its list of the fastest supercomputers in the world. In the last announcement, we continue to see Linux dominating the list. This is nothing new since Linux has been dominating since the mid-2000s. In fact, Linux share in supercomputing looks a lot like Microsoft’s historical share of the desktop market. I thought it would be interesting to take a step back and look at the performance capability of these computers as a whole and also how the rise of Linux is mirroring the geographical expansion of supercomputers.

Everybody tends to watch the number of Linux systems on the top500, but there’s a fascinating story being told by the Rmax performance numbers (Rmax is the maximum performance of a computer (measured in Gflop/s) achieved in the HPL benchmark. In many ways, this is a much more enlightening statistic, because it shows us the overall nature of performance on this list, instead of just focusing on individual computers. (This time around, five Linux systems were actually bumped off the bottom of the list, even though Linux’s *total* computing power grew by 38%.)

Linux dominance in the overall compute power of this list isn’t surprising since Linux is used in every one of the top ten computers, and especially when you consider that there is a full order of magnitude difference in performance between the first machine and the twelfth machine, which only increases as you move down the list. The first non-Linux system shows up at number 40.

Supercomputing power was on the rise well before Linux arrived, but when you look historically, it was Linux-powered machines that really caused the big ramp in the mid 2000s. In fact, when you graph the historical Rmax results of the top500 by OS, you can see that not only has supercomputing gone almost entirely to Linux, it’s also been the only OS driving the exponentially rising curve since 2005.

Next let’s look at where this is happening. This time Fujitsu of Japan tops the list. We have also seen players from China and Europe entering the fray. What’s really interesting is when you look at how this is distributed worldwide, and the role that Linux (including Linux machines that are classified as “Mixed,” like BlueGene) plays in making this happen.

It’s not surprising that the list has become very geographically diverse over time. What’s interesting is that this, too, is being driven almost entirely by Linux. In the graph below, all of the colored segments reflect the computing power deployed on “Linux” and “Mixed” machines in countries around the world. Blue is the US, white is Japan, red is China, orange is France, yellow is Germany, and so on. The dark segment on the bottom is all of the computing power deployed worldwide on platforms _other_ than Linux. Notice anything? (Here’s a hint, look at what OS is enabling this national diversity in supercomputing.)

Last, the good news here is that the there is more and more raw computing power being made available on a global basis thanks to Linux - and a lot of this innovation is making its way back into the kernel. As more countries start to use smart grid technology or seek to forecast the effects of global warming there is one common thread – the need for more computing power is endless. Just like what we’ve come to understand about Watson, (other than embarrassing humans at Jeopardy!), this technology will be used in smaller systems as we address one of the more pressing business issues of today - big data.

Once again these numbers are great for Linux. But more than numbers,, it is Linux’s ability to provide access to source code for anyone, to be optimized and have those optimizations returned for the common projects for ever increasing innovation that has created an unbreakable virtuous cycle in computing. I would also like to take this opportunity to congratulate our platinum member Fujitsu, who has done impressive research and development on Linux in super computers and for the enterprise, and who in this announcement has taken the number one position.

View the original article here

In the never-ending quest for task-management software, most Linux users gravitate towards fancy GUIs, multi-faceted import/export, and endless customization. Sadly, all that achieves is a cornucopia of incompatible GUI to-do managers, and when one goes dormant, the others are no help. But if you take the "less is more" approach instead, you'll find todo.txt a worthy alternative. Todo.txt stores its data in a flat text file that any application can read, but it gives you full access from the command line as well as from Android and other mobile devices.

Technically speaking, the command line interface is properly called either todo.txt-cli (which is the name of its public Github project) or todo.sh (which is the name of the actual script you use to add, update, prioritize, and assign tasks). But for most people, todo.txt is the preferred moniker, because it highlights the key feature — the plain-text, human-readable, and "future-proof" todo file. The CLI script is the canonical way to access and change the file, but its simple format had led to a healthy ecosystem of other front-ends, including web-based and Android interfaces.

The principle of todo.txt evolves directly from a simple text file listing one task per line, with a minimum of syntax added on. In fact, according to the wiki documentation, there are just three features that todo.txt views as essential: prioritization, projects, and contexts. Prioritization simply allows you to sort tasks by importance, and is denoted with parentheses: (A) is a "most important" task, (B) is second-most important, and so on. Each "project" is a grouping of related tasks, and a project name is indicated with a plus sign, such as +RoofRepair, +Thesis, or +WorldDomination. Contexts are directly borrowed from the Getting Things Done (GTD) approach popularized by David Allen, and are denoted with an at sign, such as @home, @phone, or @undergroundlair.

The kicker is that none of these syntactic features are required. A perfectly valid entry in todo.txt is as simple as:

Buy root beer

... but you can layer on the other features as desired, and with the exception of priorities, in whatever order feel natural. All of the following are valid entries as well:

(A) Buy root beerSolve Rubik's Cube +SelfImprovement @work(D) +Music +Backyard Install Outdoor Speakers @homeFind lost wallet @home @office @car @park +Life +Finances +RememberingThings

Priorities have to come first, for parseablity's sake — that way if you need to add the task "Turn my side business into a registered 501(C)(3)," it's unambiguous. Some of the front-ends also add creation dates, and if you use them, they either have to come first or directly after a priority indicator, using the YYYY-MM-DD format. This also prevents ambiguity.

Your task list can also include completed items — for various reasons, you may need to retain them in the file even after you are finished with them. The official syntax for a completed item is that it starts with an X (or a lowercase x) followed by a space. Which means if "X-ray" or "X-Men" happen to start one of your to-do items, be sure not to forget the hyphen. If a completed item has a date immediately following the initial X-and-space, this is officially interpreted as the completion date. That could result in some ambiguity in tasks that already started with a date, depending on the front-end you use, so several of the add-ons use their own metadata format such as due:YYYY-MM-DD. But you don't need to worry about that to get started.

The file format, therefore, is simple. Using it is also simple, thanks to the todo.sh shell script. The downloads page hosts bundles in .tar.gz and .zip archive formats, which hints that the package is usable on a variety of operating systems. The latest release is version 2.7, from August 2010. Inside the archive you'll find two files: todo.sh (the script) and todo.cfg (its configuration file).

The todo.sh script is written for Bash, the default shell on most Linux distros. But when it says Bash, it means Bash: not csh, sh, ksh, or that shell your lab partner wrote. Quite a few users have posted questions on the mailing list about mysterious errors that trace back to not having Bash installed, and the system falling back on a slightly-incompatible shell.

You can install todo.sh anywhere, just make sure you make it executable with chmod +x todo.sh. Open the todo.cfg configuration file in a text editor, and edit the "Your todo.txt directory" line to reflect where you want to keep your main todo.txt file, archives, and various ancillary files. If you're not sure, try /home/yourusername/.todo — but also make sure to create the directory you specify. You can dig into the config file some more and play with color settings and list-sorting preferences, but that is optional.

The wiki suggests a few other tips, such as adding a Bash alias to save on typing. Adding alias t='todo.sh -d /home/yourusername/todo.cfg' to your .bashrc lets you access todo.sh just by typing t. The -d switch is recommended because todo.sh supports multi-user use in a system-wide installation, and each user needs a separate config file.

Speaking of usage, to add a task to your to-do list, type t add "Write the Great American Novel" — optionally including any +Projects or @contexts as needed. The only rule is that you must place quotes around your task text. To see your list of outstanding tasks, type t list or t ls. Todo.sh will write a numbered list of your tasks (along with a summary) to the screen. The number denotes the order the tasks were added. For example, you might see

01 Write the Great American Novel02 Quit job03 Move to @TropicalIsland--TODO: 3 tasks in /home/nate/.todo/todo.txt

If you add a project, context, or priority as an optional filter to the end of a list command, you can see just those tasks that match. So t ls @home shows you your "home" context, t ls +ServerUpgrade your "ServerUpgrade" project, and so on. But you can also pass any chunk of arbitrary text to an todo.sh ls command, and the script will return those to-do items that match it, so t ls cupcakes is perfectly valid, too.

You assign priority flags to tasks with the pri command, followed by the task number (as ls lists it) and the letter of the priority you want to attach (A through Z), such as t pri 16 A. Subsequently, when you do an ls listing, tasks that have priorities assigned will be color-coded and placed at the top of the list, sorted in order. The depri command removes the priority flag from an item.

When you complete a task, mark it with do followed by the task number. In other words, t do 8. Task 8 will be flagged with an "x " in the todo.txt file, and no longer listed for you when you type an ls command.

On top of the basics described here, the todo.txt community has written several add-ons that supply additional functionality, such as grouping ls output by project, assigning "threshold dates" in the future (so that items do not appear in the list until they are slated to start), and pretty PostScript output for printing. These add-ons are scripts that live in their own directory, which is specified in todo.cfg.

If you never leave home, a GTD-capable task manager that you can use entirely from the terminal is reason enough to look at todo.txt. In fact, because you can use todo.sh over SSH, maybe you never do need to leave home. For that matter, todo.sh runs perfectly well on Maemo handhelds (if you remember to install Bash) and should work on MeeGo and Android devices, too. But for the sake of argument, let's pretend there are times when the command-line orientation of todo.sh isn't what you want. There are several alternatives to keep your tasks in sync while you're on the move.

The first is Todo.txt Touch, a full-featured Android client written by the todo.sh maintainers. You can download it from Github, or look for it in the Android Market (although it is not free in the market, the code is exactly the same as the freely-downloadable version). It sports on-screen buttons for the basic functions (adding, filtering, and flagging tasks, assigning priorities, contexts, and projects, etc.) and uses Android's built-in text-input mechanisms to enter task details. There is a simple one-click interface to access your list of projects and contexts, which really is nice (even if it is flashier than the shell script's text output....).

More importantly, Todo.txt Touch is designed to sync with a remote storage location. As of right now, the only supported service is Dropbox, but the team indicates that more "cloud" storage services are to come. If you want to keep your Todo.txt Touch and your CLI task lists synchronized, all you need to do is open up your todo.cfg file and point the todo.txt directory variable to the proper location in your Dropbox folder.

But wait, there is more. Those users with iPhones will appreciate todo.txt-web, which is a PHP-and-jQuery based front-end to todo.sh that you can use as a web app. This requires making the todo.txt files writable by your web server, but is otherwise based on the same code. The default CSS styling of the front-end is designed to look like an iPhone web-app, but the code should render equally well in any modern mobile browser.

Finally, for those users that use the Remember The Milk web service, there is a separate Bash script called getmilk.sh that fetches a remote list of RTM tasks and re-formats them into todo.txt-compatible syntax.

Any way you slice it, Todo.txt's power comes directly from the simplicity of its file syntax. You can use the shell script, the Android app, a text editor, or any other tools you devise to edit the file (there is even one written in .Net for Windows users). As long as the applications retain the correct syntax, any of the other front-ends can make use of the result, so you can Get Things Done whether you're in front of the keyboard, on a remote machine, or in the middle of nowhere with only your phone by your side.

View the original article here

The Mageia project has published a first preview of a Mageia port for ARM processors. The port, code-named "arm eabi", includes several development tools, basic network services and a full GNOME desktop environment - a minimal version of KDE is also included

View the original article here

Picking a Linux distribution isn't always easy. It's one of the most common hurdles for new and aspiring Linux users, deciding which distribution is going to be right for them. With so many to choose from, how do you pick the right one? Let's start with an overview of the major Linux distros, and you'll be ready to jump in right away.

You can find hundreds of Linux distributions, depending on what your needs are. For this scorecard, we're focusing on desktop distributions that are fairly popular, well-supported, and have a reliable release history, and strong community. In last year's scorecard, we started with seven distros — this year, we've narrowed the field to six distributions:

DebianFedoraLinux MintopenSUSESlackwareUbuntu

This isn't to say that a distribution isn't the bee's knees if it's not on the list — but we want to start with a manageable selection for new users. If you want to start at the easy end of the spectrum, we've got good choices for you — and if you want to get your hands dirty and learn all about Linux, we've got a few distros that meet those needs as well.

Which distribution is the best? None of them, or all of them. It's really about what meets your needs. Some people want a distribution that's really easy to use, and don't care much about licensing. Some people choose a distribution because of the licensing, and ease of use isn't really that important. You might only want to look at distributions that have KDE or GNOME as a desktop. It's sort of like picking a restaurant, what makes one person happy is going to be a really bad experience for another person. I like spicy food, other folks can't handle it or just don't like it. What we're doing here is letting you have a peek at what's on the menu so you can decide where you'd like to start.

As with last year's scorecard, the criteria for choosing distributions were the major Linux desktop distributions that have demonstrated longevity, a strong community, and stability. Naturally, that means the majority of Linux distributions aren't listed here, so if your favorite didn't make the cut — don't take it personally. Do feel free to talk about your favorites in the comments, and offer other helpful suggestions for new Linux users.

To start with, let's look at Debian. Debian is an entirely community developed Linux distribution with no single commercial backer. Many companies contribute to Debian in one way or another, but it's a purely independent project. Debian has a large developer community, and is used as the base for Ubuntu, Linux Mint, and a number of other distributions. The distribution started in 1993, founded by Ian Murdock — but out of humble beginnings, it's grown enormously.

Debian has a very developer-centric community, though the project has recently welcomed non-packaging contributors to explicitly acknowledge contributors who write documentation, create artwork, perform translations, and so on. Debian has a Social Contract that requires the project remain free, give back to the larger community, be open with problems, and to be guided by the needs of its users and the free software community.

Debian has an intense focus on technical excellence and shipping free software. With the most recent release, the Debian project rid its Linux kernel of all non-free firmware ("binary blobs"), though the project does continue to offer kernels with the firmware in the non-free repos. Debian does allow some non-free repositories, but they're not "officially" part of Debian.

Debian's release schedule is "when it's ready," and not before. The distribution ships at irregular intervals, though users don't have to wait for stable releases to use the latest and greatest. Many Debian tend to run the testing or unstable branches. Testing (which will be the next stable release) and unstable have more current, sometimes bleeding-edge software — but are also for more experienced and adventurous users. You probably shouldn't run Sid (unstable) unless you have a thirst for adventure and want to get some experience troubleshooting. This isn't to say it breaks a lot, but when it does, it could be spectacular.

Debian stays close to upstream with its packages, and offers a minimum of customization and polishing. Compared to distributions like Ubuntu or openSUSE, Debian makes very few changes. This isn't to say no changes, but there's minimal rebranding and such for Debian compared to some of the major distros that are trying to appeal to a less experienced audience.

You'll get very little hand-holding with Debian. The installer is fairly complex when compared to other distros, and you will have to do much more configuration manually. Users need to make more decisions about which packages to install initially, will find fewer management tools, etc.

Debian is a distro of choice for users who want to install Linux on an older non-Intel machine. You can run the most recent stable release on x86, AMD64, ARM, PowerPC, Itanium, MIPS, SPARC, and IBM's S/390. Note that Debian dropped support for PA-RISC and Alpha chips with the Debian 6.0 ("squeeze") release.

Debian is also unique in our list because the project now offers a FreeBSD-based release as well, so if you want the Debian userland software with a BSD kernel, you can give it a shot. Not only does Debian support an enormous range of hardware, it also has an extremely large package selection. The packages in the stable release are likely to be a bit behind the upstream's most recent release, but if you want to track new software you might want to run Debian testing or unstable.

Debian is an open project, but it doesn't have as many resources to induct new contributors as Fedora, openSUSE, or Ubuntu. Overall, Debian is best-suited for more experienced Linux users or those who want to learn more about their systems. It's also an ideal distribution for those who are dedicated to the ideals of free software. If you want a distribution that "just works," you probably won't enjoy Debian as much. But without Debian, many of the "just works" distros would not exist.

The Fedora Project is sponsored by Red Hat, but has a fairly diverse set of contributors outside the company as well. The project has its focus on innovation, freedom, and community contributions.

Fedora has a six-month release cycle, but releases often slip if they're not up to quality standards — almost every release cycle has a few slips. But the release dates tend to be close enough to the schedule that users have a fairly good idea when the next release is going to be out. Tracking release dates can be important — the releases are only supported for about 13 months. Users who don't want to upgrade frequently should choose another distribution. But if you want to ride the "cutting edge," of software, Fedora is going to be an excellent choice. Fedora ships the latest software that's stable, or (in some cases) almost stable. New technologies often debut in Fedora.

Fedora is fairly user friendly, but can have a few rough edges. It's not always as polished, and sometimes Fedora ships software that's brand-new — like with the Fedora 15 release that ships with GNOME 3.0, a new init system, and more. The next release is expected to default to the Btrfs filesystem, another technology that's not been widely deployed. Part of shipping "cutting edge" software means that you may encounter some packages that are less than 100% stable, or may not be feature complete. It is worth noting that the quality of the distribution has improved greatly since the early days of Fedora. If you're comfortable with computers and not afraid of the command line, Fedora is a good distro to consider.

If software licensing is important to you, Fedora is one of the top distributions to look at. The project only ships free software, and won't ship media codecs or much else that's not open source or might be legally encumbered. You may have to do some extra work to get MP3 or DVD support, but that's part of the price of freedom.

Fedora takes software freedom very seriously, and makes its tools and infrastructure free as well. If you want to set up a Fedora derivative, it's not hard to do. The project supports a number of spins (Fedora-based distros that differ from the default set of software), and has the tools for users to create their own. Whether you like GNOME, KDE, Xfce, LXDE, or another desktop, you're good to go.

The management tools and installer are fairly good, though they assume some understanding of Linux. The management tools aren't quite as comprehensive as openSUSE's YaST, but you'll be able to do most system administration using GUI tools if you choose to. You'll also find a fair assortment of third-party packages and support for Fedora, including hosting providers that offer Fedora as an option if you want to extend your Fedora use to a hosted server.

The hardware support is more limited than Debian, though — so no Itanium or MIPS for you. If you have x86 or AMD64 based systems, though, you're good.

Generally, Fedora is OK for new users, but might not be the best introductory Linux distribution. It's great for experimenting with new technologies, and to see what's coming in the future for Red Hat Enterprise Linux (RHEL). If you're a developer, Fedora is also a great choice. You can get involved in the Fedora community very easily, no matter what your skill set. The community is friendly and works hard on recruitment for new contributors.

Linux Mint has undergone a lot of change in the last year. Historically, Mint has been based on Ubuntu (which is in turn based on Debian, of course). In September, the Mint folks introduced a Debian-based release in addition to the Ubuntu-based main release. What does that mean? Users who want to get the most polished and stable release should choose the main Mint release, which is based on Ubuntu. Users who want to use a "rolling release" distribution should look at the Debian version.

Whether you go with LMDE (the Debian version) or the usual Mint release, you'll get an easy to use installer, slick package management tools, and out of the box support for MP3s, Flash, DVDs, etc.

Many of Mint's packages come from Ubuntu, but the project does customize or provide its own packages for some software. You'll also note that the latest Mint release (Mint 11) does not share Ubuntu's default desktop — instead, Mint 11 sticks with GNOME 2.32 and is taking a more conservative approach to its desktop. Because of its Ubuntu heritage, Mint has decent third-party support. You'll be able to install packages for Ubuntu on Mint most of the time with no problem.

The Ubuntu-based release also follows Ubuntu's development cycle, but trails by a few months. So when Ubuntu 11.10 is released in October, for instance, you'll see a final release of Mint 12 a few weeks afterwards. Support, likewise, follows Ubuntu's schedule. You get 18 months of support for regular releases, and three years on the desktop for Long Term Support (LTS) releases. The LTS schedule is determined by Ubuntu, of course &mash; but there tends to be an LTS release about every two years. These are strongly recommended for folks who want to install Linux for friends and want to have a hassle-free support scenario.

The Debian-based release is a rolling release, which means that there are fewer releases but you should be able to track LMDE by installing just once. If you're unsure which release to choose, go with the the standard release. Note that you can also grab a release that doesn't include the multimedia support, if you're worried about running afoul of the law with patent-encumbered codecs and such.

Mint has a friendly community, though contributing to Mint is not as easy as other distributions. The core team is small, and there's not a major focus on contributing. However, the Mint folks say they're willing to take contributions and dedicated contributors have launched Mint flavors based on KDE and LXDE.

Mint is x86 and AMD64 only — no support is forthcoming for PowerPC, SPARC, etc.

The bottom line on Mint? It's a great distro to start with if you want a replacement for Windows and want a distribution that "just works" right after the install.

View the original article here

With the Linux 3.0 kernel carrying CleanCache support along with various improvements to the EXT4 and Btrfs file-system modules, it is time for another Phoronix file-system comparison. This time around the EXT4 vs. Btrfs performance is particularly important with Fedora 16 possibly switching to Btrfs by default. Due to this level of interest, for our Linux 3.0 kernel benchmarks of the EXT4 and Btrfs file-systems, an Intel SSD was tested as well as an old 5400RPM IDE notebook hard drive to represent two ends of the spectrum.

View the original article here

As mentioned last week, a plethora of Linux power tests are on the way now that we have found an AC power meter with USB interface that works under Linux and we've been able to integrate nicely into the Phoronix Test Suite and its sensor monitoring framework. In this article is one of the first tests that have been completed using this power-measuring device as we monitored the Linux kernel power consumption for an old Intel Pentium 4 and ATI Radeon 9200 system for the past several kernel releases. Even this very old desktop system looks to be affected by the kernel power problems.

View the original article here

The Creative Commons project has announced the release of a 47-page book highlighting the stories of a number of people using CC licenses for their work. "The Power of Open collects the stories of those creators. Some are like ProPublica, a Pulitzer Prize-winning investigative news organization that uses CC while partnering with the world's largest media companies. Others like nomadic filmmaker Vincent Moon use CC licensing as an essential element of a lifestyle of openness in pursuit of creativity. The breadth of uses is as great as the creativity of the individuals and organizations choosing to open their content, art and ideas to the rest of the world." Unsurprisingly, it's downloadable under a CC license.

View the original article here

Coincidently there's some more file-system news after just writing about the EXT4 and Btrfs file-systems with the Linux 3.0 kernel. A Phoronix reader has pointed out that a developer at Tuxera is claiming their proprietary NTFS Linux kernel driver makes the Microsoft file-system the fastest choice under Linux. Reportedly this kernel driver that implements Microsoft NTFS support is about twice as fast as EXT4, the main Linux file-system of choice right now...

View the original article here

James Simmons has written a status update to the OpenChrome development list concerning his ongoing work towards enabling kernel mode-setting (KMS) support for VIA hardware with this community-maintained VIA Linux project...

View the original article here

Simon Crosby, previously the CTO of Citrix System announced today that himself, Ian Pratt, previously VP of Engineering of Citrix Systems and Chairman of Xen.org, and Gaurav Banga, creator of Phoenix Hyperspace are launching a new startup, Bromium, Inc. Read more

View the original article here

DNS Service Discovery (DNS-SD) is a component of Zeroconf networking, which allows servers and clients on an IP network to exchange their location and access details around the LAN without requiring any central configuration. Most Linux distributions supply the Avahi library for Zeroconf support, but not nearly as many users take advantage of it. Let's look at an easy-to-set-up use for DNS-SD: providing automatic bookmarks to services. All it takes is an Apache module and a Firefox extension.

The essence of DNS-SD is that Zeroconf-supporting applications or hardware devices broadcast a DNS SRV record (of the kind typically used in static DNS to point to a host and port number combo) advertising themselves, and everyone else on the network hears it and takes note. They make the broadcast over multicast-DNS (mDNS), which is a protocol derived from normal DNS, but using special, local-only "multicast" addresses and the reserved .local pseudo-domain.

The system is akin to Universal Plug-and-Play (UPnP), except that it handles more types of services, and builds more directly on top of DNS. The mDNS/DNS-SD pair's major backer is Apple, and UPnP's is Microsoft, so as you might guess, neither is likely to give up and start supporting the other. There is hope for a unifying IETF protocol in the future, but at the moment mDNS/DNS-SD is well-supported enough by the open source Avahi library that Linux users can start working with it today.

In the Apple world, printers and chat clients commonly use mDNS to advertise their availability. But there is a long list of application types that can advertise over the system, including VoIP clients and servers (such as Asterisk), closed-circuit video devices, even collaborative editors (such as Gobby). Essentially, any service that can be described in a SRV record can be advertised; it just needs to provide a service name, a transport protocol (TCP or UDP), and the port and hostname of the server where it can be reached. The mDNS .local domain allows participating devices to assign themselves reachable hostnames.

With the server properly configured, the DNS-SD stack on any client machines will catch and catalog the local services automatically, for use by applications on the system. On a Linux box, Avahi hears and notes the mDNS messages, and an interested client (say, a chat app) asks Avahi if there are any XMPP servers nearby to talk to. The connection is made, and voilà, you start chatting.

It's easy to imagine how DNS-SD could take the pain out of some typically hard-to-configure applications like VoIP, but if you are new to DNS-SD there are simpler places to start, such as with good old-fashioned HTTP web servers. If you're like me, your main Linux box is running a variety of web interfaces for local services: phpMyAdmin, CUPS administration, Webmin or another config tool (in my case, I also have an X10 home automation front-end and the MythWeb MythTV interface running). You may also have work-related services running, such as a Bugzilla instance or network administration workspace, or even a straightforward Intranet site.

The unifying principle is that these are all web services you might like to access from more than one machine on the LAN. You can manually enter the bookmarks on every machine, or use a synchronization tool like Firefox Sync or XMarks, but these strategies make you choose between repetitive work and potential security risks -- not to mention they require updating all of the client machines whenever there is a change. That is precisely the problem Zeroconf networking was designed to solve.

Developer Andrew Tunnell-Jones has written a small but highly useful extension that adds DNS-SD support to Firefox. The code is hosted at Github, but you can install the extension itself, "DNSSD for Firefox," through the addons.mozilla.org site. It requires Firefox 4.0 or later (no word yet on the just-released Firefox 5; it doesn't appear that anything relevant has changed in Firefox itself, but the add-ons system is notoriously pedantic about version numbers), and a working Zeroconf implementation. For Linux, Avahi works just fine, and Mac OS X users will already have Apple's Bonjour installed. Windows users can install the Apple-provided Bonjour-for-Windows package, which Tunnell-Jones links to from the extension page.

After you restart Firefox, the extension adds a menu labeled DNSSD to the Navigation toolbar (between the forward/back buttons and the URL bar) and to the Bookmarks menu. Click on it, and you will see a list of all of the local HTTP servers detected by your Avahi or Bonjour service: no configuration necessary. If you want to double-check the extension's list, you can run avahi-browse --all from the command line.

If you are running GNOME, you should also see a desktop notification pop up whenever the extension notices a new service (although for most services, this will just be at start-up time). That option is configurable in the preferences, which you can get to through the Add-ons Manager.

It works, and it is automatic, but there are a few quirks to be aware of. First, you don't (yet) have the option to choose where the DNSSD menu is displayed. Placing it in the navigation toolbar makes sense because that is the one toolbar almost guaranteed to be present, but putting it in the Bookmarks toolbar would seem to make more sense to me -- it seems like a natural complement to Firefox's automatic "Most Visited" and "Recently Added" bookmark folders. Second, although you can access the DNSSD menu through the Bookmarks menu, you cannot move it around in your bookmarks to a more convenient location. I asked Tunnell-Jones about both of these options, however, and it sounds like they are possibilities for future releases.

You can probably think of a handful of local web services you would like to automatically advertise around your office or home network, but the odds are that most of them do not advertise over mDNS out-of-the-box. In my case, the only running server that did provide a web interface over DNS-SD was the MT-DAAP audio server. To get your other services to announce themselves, you'll need mod_dnssd.

Mod_dnssd is an Apache module that adds simple mDNS/DNS-SD support to your Apache-hosted sites, with a minimum of configuration fuss. The latest release is 0.6, which supports Apache 2.2, although there are older releases for those still running Apache 2.0 for some reason.

The author, Lennart Poettering, is best know as the maintainer of PulseAudio (which, yes, uses mDNS/DNS-SD to locate other networked PulseAudio sources on the LAN). The docs on the site are a nice introduction, but Poettering has written a more extensive how-to on his blog. To get it working, you'll need to install the module (packages are available on the site, but most distributions offer it as well), and make sure that Apache loads it at startup (check your distro's documentation for details, or edit your /etc/apache2/apache2.conf if installing from source).

To use the module, you must first activate it by placing the DNSSDEnable on directive in the Global Environment section of apache2.conf. With that configuration alone, Apache will advertise all of the VirtualHosts over mDNS/DNS-SD -- however, clients will have trouble connecting to them if you do not label your VirtualHosts with fully-qualified domain names.

For a little more fine-grained control, you can add a DNSSDServiceName "Whatever You Want To Advertise It As" directive to each VirtualHost or Location block. The ServiceName you assign will be the user-visible label seen in the DNSSD menu offered by the Firefox extension, so you can give easy-to-remember, LAN-wide labels to your bug tracker, Apt-CacherNG control panel, or any other site. But remember to include the server's name if you are running multiple web servers on the LAN, lest your users get confused.

By default, mod_dnssd advertises Apache resources as HTTP services (i.e., using the _http._tcp SRV record). That makes sense for most web services, but you can also alter it to properly advertise other applications, such as WebDAV or RSS feeds. Simply add the DNSSDServiceTypes directive to your Apache configuration, followed by a space-separated list of the service types you wish to advertise -- either for the server as a whole, the VirtualHost, or the Location, depending on where you put the directive.

Obviously, the Apache plus Firefox combination only scratches the surface of what DNS-SD as a whole is capable of, but as an increasing number of services use HTTP, it is at least a useful place to start. You can save yourself some trouble by DNS-SD-enabling your Intranet sites and letting your users find them automatically. Of course, you do still need to take precautions to protect your services. The DNS-SD services will only be visible to LAN clients, but if you do not want that to include WiFi visitors, you should partition them off into a different subnet altogether -- and it goes without saying that your admin panels ought to be password-protected.

But there is another subtle condition imposed by this scheme: it requires changing Firefox, the client application. So although it's easy to imagine DNS-SD-advertised bookmarks being useful in a public environment (say, an Internet cafe), you still cannot expect visitors wandering in off the street to have the right extension installed. In my mind, DNS-SD, like Microformats, is a technology that Firefox really ought to support off-the-shelf. There is no reason not to, unless you make the security argument -- but honestly, a service at risk is not any better-protected just because it is un-advertised. Maybe Tunnell-Jones's extension will have a hand in raising awareness of the convenience offered by DNS-SD. At the very least, you can leverage that convenience yourself, and that's a pretty good start.

View the original article here

Often the most impressive thing about the open source community is getting to watch someone step up to work on a task that's far from fun or glamorous in the traditional sense. A good example of that phenomenon is Damon Lynch's Rapid Photo Downloader (RPD), a utility that takes the pain out of what many projects overlook: getting your newly shot material off of the camera's memory card and into your computer. Despite the name, RPD handles both photos and video, and although its speed is impressive, how it really makes your life easier is by keeping you and your storage organized.

The root "problem" that RPD sets out to solve is what happens when you plug your digital camera or camera memory card into your Linux computer. The default behavior is for a desktop tool to pop up, usually a GNOME or KDE front-end to gPhoto2, the standard image-transfer library. The tool knows where in the flash memory hierarchy to find the actual image files (including the separate storage schemes for raw and JPEG images), and it copies them to the hard disk and optionally erases them from the card.

That sounds simple enough, but more often than not, Linux distributions don't use a file-manager tool to handle the task. Instead they hand it off to a full-featured photo management app, which takes considerably more time to step through the process, often filing images in its own internal database, making thumbnails, and other bookkeeping jobs. While that might be a tolerable overhead for a 1 or 2GB card, when you hit 16 or 32GB, it becomes agonizingly slow. If you're on notebook battery, it is even worse.

Compounding the problem, no two photo-management apps can agree on where to store things: ~/Photos, ~/Pictures, ~/MyPhotos, etc. Even if you're a good Linux citizen, every few releases the distros change their default app set, and you eventually find your photos scattered around a half-dozen locations. That makes images hard to find, easy to lose, and easy to forget when you're migrating computers or making backups.

You can download RPD from the project's Web site. The team has detailed instructions provided for Ubuntu, Fedora, Debian, Mandriva, and several other distributions. In most cases, there is either a prepackaged version of RPD available from the distro, or a simple-to-add repository. The latest release is version 0.4.1, a minor update from May of this year.

After you've installed RPD, you can launch it from the Applications menu or from a terminal with rapid-photo-downloader &. RPD is built on GTK+ and some GNOME underpinnings, but it runs just as well in KDE and other environments, since the only key dependency is Python. How you get RPD to actually launch automatically when you attach a camera or pop in a memory card varies, though. In GNOME, go to the "Removable Drives and Media" option in Preferences, and enter rapid-photo-downloader as the command to import photos when a device is connected. In KDE, the setting is found in "System Settings" -> "Device Options."

With RPD, you are in control of all of the options. The preferences dialog lets you choose any folders on your system as target directories (including separate settings for photos and videos), and optionally allows you to auto-create sub-folders to further structure your archives. RPD can offload media from multiple devices at once, so you can get the maximum performance our of your system by, for example, connecting your camera via USB cable while popping another memory card into the card reader slot.

In its simplest form, the sub-folder feature lets you split up your collection in sub-folders by year and month, which makes backing up to non-volatile media considerably simpler. But you can also configure sub-folders to split up images by their filetype (e.g., keeping raw and JPEGs separate), by automatically-gathered metadata (such as camera model), or by "job codes" that you define yourself ("work" and "personal" come immediately to mind).

A related feature is RPD's auto-file-renamer. If you have a naming scheme in mind, RPD lets you set up a renaming formula in "set it and forget it" mode, using the same options available as sub-folder choices. A big benefit to this technique is keeping more than one image source straight. Not every camera allows you to control the file name and file-numbering settings it applies to new material, and these days almost everyone has one "real" camera plus a cameraphone. RPD can massage the less-flexible filenames into the same format as the rest.

The RPD project makes a big deal out of its speed. On top of the name itself, the home page boasts of a 2.5x speedup over F-Spot and a 12.5x speedup over Shotwell. I don't think those numbers are scientific, but RPD is certainly faster. Even more so when you factor in offloading from two cards at once and the instantaneous file-rename feature, which saves an entire step.

Speaking of saving steps, in my mind one of RPD's signature features is the ability to automatically save backup copies of your media. As a member of the non-elite club of those who have had a laptop drive fail while on the road, I always carry a 2.5" external drive with me to save a second copy of any files I shoot (the first being on my laptop). RPD will write backup copies of each file to a directory you specify, and can even do so at the same time it saves the main copy. This assumes your bus bandwidth can keep up; if you are also doing multi-device offloading, you would probably be better off serializing some of your tasks...

As with the main file operations, you can specify separate settings for photos and videos, and RPD will automatically detect all removable storage media, so you can save backups in more than one place if you desire. RPD also allows you to configure some automated behavior, such as starting the offload (and backup) process as soon as the program launches, unmounting removable devices when offloads are completed, and so forth. A handy feature you are likely to only appreciate on rare occasions is how RPD handles name collisions — such as when two auto-renamed files somehow would end up with the same filename. Finally, RPD can automatically sanitize filenames and folder names to ensure compatibility with lesser, non-free operating systems.

For 90% of RPD's users, the basic offload and backup features are more than enough — well, assuming that they use backups, but then again, that is part of the point. RPD builds that easy-to-procrastinate task into the plug-and-play, normal operation. High-end users are more likely to appreciate the flexibility of subtle things like automatic file renaming and directory creation. After all, if you only take a few pictures or videos a year, opening up your Photos folder in Nautilus or Dolphin and browsing by thumbnails might be all the asset management you need. It's with hundreds that that method breaks down.

I'm a big proponent of the "let each tool focus on its own thing" approach. As such, I don't like it when a photo editor decides it knows better than I do where I want my images stored or how I want them organized. Ubuntu frequently changes which iPhoto clone is the preferred photo-management app, and honestly I don't find any of them to be particularly good, or particularly good at guessing what I want. It works far better to have a dedicated image offloader like RPD launch when I plug in a memory card. Thus, regardless of whether I choose to fire up Digikam, GIMP, Rawstudio, or a Flickr exporter, I know that my collection is in the same place. Oh, and I know that there's a backup copy on a removable drive, too — even if I forgot about it when I sat down at the keyboard.

View the original article here

The Linux Foundation Video Contest this year is different. For the first time, we're running it mid-year and more importantly, it is one of the ways we're celebrating the 20th Anniversary of Linux. Here are five more reasons to submit a video this year! Deadline is July 2, 2011.

1) Linus. Linux creator Linus Torvalds is choosing the ultimate winner this year. No one has a better sense of humor, or competitive streak, than Linus. Winning this year's contest will get you some real community cred. Don't be intimidated. No flames.

2) Planes, trains and automobiles. You get a free trip, people. And, you get to choose from four different destinations depending on which event you choose to attend as the winner: LA Film Festival (Los Angeles), SXSW (Austin, Texas), LinuxCon North America (Vancouver, B.C.) or LinuxCon Europe (Prague).

3) You'll go down in history. This year's winning video will become *the* 20th Anniversary of Linux video. It will be hosted here on the widely visited Linux.com website and The Linux Foundation's YouTube Channel, as well as promoted to hundreds of thousands of people on The Linux Foundation's social channels.

4) Get skillz. If the only thing you've ever shot is your kid eating applesauce but you had a great time doing it...winning this contest could open up a new outlet for your creativity or even get you noticed and open up a new career path.

5) Make a difference, inspire. Linux invokes passionate emotion from the people who use it and who are involved in its development. Linux is the largest collaborative development project in the history of computing. It set the expectation that software, hardware and much more could be built collectively. Your video could plant the seed for the next inspiration to come from Linux.

View the original article here

The second and final RC for version 3.2 of the open source blogging and publishing platform, which addresses several bugs found in the previous release and "tweaks" the new default theme, has been made available for testing

View the original article here

Red Hat's Eric Sandeen has written an interesting blog post concerning the size of popular Linux file-systems and their kernel modules. It turns out that the XFS file-system is losing lines of code, while maintaining the same feature-set and robustness, but the EXT4 and Btrfs file-systems continue to have a net increase in lines of code...

View the original article here

E3, the Electronic Entertainment Expo, is officially kicking off today in Los Angeles and will be running through Thursday. This, along with the Game Developers Conference, is one of the key times of the year for the electronic gaming industry. A number of game studios will be announcing new titles and other great announcements, but will there be anything Linux related?..

View the original article here

New release sees a major boost in handling small objects at over 200,000 requests per second in benchmarks. Traffic Server also builds on Mac OS X, Solaris and FreeBSD now...

New release sees a major boost in handling small objects at over 200,000 requests per second in benchmarks. Traffic Server also builds on Mac OS X, Solaris and FreeBSD now

View the original article here

When you release code under the GNU General Public License (GPL), you undertake a specific set of obligations. Many of these obligations, such as providing a copyright notice and a copy of the GPL version you are using, are relatively simple.

When you release code under the GNU General Public License (GPL), you undertake a specific set of obligations. Many of these obligations, such as providing a copyright notice and a copy of the GPL version you are using, are relatively simple. However, the obligation to provide source code with the object code is more complex, because you have several choices about how to fulfill it – and the choice you make can cause ongoing problems, especially if you are not set up to administer it.

View the original article here