Fresh from the Labs
This is a lovely little application that gives you very little grief. Think halfway between Amarok and Kaboodle, and you'll get the idea. For those of you who just want to play a few files at a time and hate fancy music players with more features than you could ever want, Minirok is for you. The player is minimalistic and dressed-down, but it still allows for features, such as playlists, skinning, Last.fm support, keybindings and DCOP support for KDE integration. According to Minirok's Web site:
Minirok is a small music player for the K Desktop Environment. As its name hints, it's modeled after Amarok, but with a reduced set of features. In particular, it is designed to cover all the needs and wishes of the author, leaving everything else out. The look and feel is almost identical to Amarok's, though. The main interface is a tree view of the filesystem, with a playlist that can be populated only via drag and drop. There is no collection built from tags, so it's targeted at people whose collections are already structured in a tree at the filesystem level. Searches can be performed both in the tree view and the playlist.
If you head to the Minirok Web site, both tarballs and .debs are available (the Debian packages are a little bit older than the source tarballs). As far as dependencies go, aside from PyQt and PyKDE, the only dependency that's relatively obscure is python-mutagen—a Python module that handles audio metadata. Apt users should be able to install the module via the following:
# apt-get install python-mutagen
After this command, the .deb should install, and the tarball should build with no trouble. To install the .deb package, open a terminal to the directory the .deb sits in, and use the command:
# dpkg -i minirok_0.7-1_all.deb
To install via source, download and extract the tarball. Open a terminal in the new directory, and enter the command:
# ./setup.sh install
Minirok should be in your menu under Multimedia. If not, simply run the command minirok. Once you're in, just click and drag a folder or MP3 into the window pane on the right. As far as controls go, the button on the bottom right that looks like a window clears the playlist, so if you've made everything cluttered and want to start fresh, there's your button. Otherwise, it's a simple case of skip forward or back a track, stop, play/pause and a slider bar. On the left are two buttons: the first, a downward-pointing arrow, is for repeat, and the second, a right-pointing arrow, is for randomizing. And, that's about it—really nice and minimal!
For the moment, things are fairly stable due to a minimal interface, with only the occasional bug. I found that it didn't like some kinds of MP3s, and sometimes it doesn't lead onto the next track on a playlist, but those issues seemed to be fixed in the latest tarball. Overall, this project's been my favourite this month. It fills a niche and doesn't give you all that installation grief.
If you're looking for a good tool for finding duplicate files, this is it. I've been researching these tools for a while, but I didn't trust any to touch my filesystem, as many of my duplicate files are there on purpose. Perfect Match (or pmatch for short) is non-destructive. Using the default options simply prints out a list of what files are duplicated and lets you decide for yourself which ones you'd like to remove.
As for goals and aspirations, according to author Tomasz Muras' Web site:
Some time ago, I was looking for a utility that would find (and possibly remove) duplicate files. I have found a few of them but none was complex enough for what I wanted...hence the idea of Perfect Match! My main requirements were quick compare—that is, first compare files based on size, then hash—and to perform some logic when choosing which duplicate should be removed.
For the moment, there is no installer available for pmatch, so you'll have to take a few steps here and there, but thankfully, not too many, as it's a small project. The main dependency is Ruby, and a subproject called RubyGems—a system for managing Ruby software libraries. Chances are that RubyGems already is in your distribution's repository, so doing a simple:
# apt-get install rubygems
John Knight is the New Projects columnist for Linux Journal.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide