Fresh from the Labs
will work for most people. If not, check out the RubyGems home page (rubgems.org). Once RubyGems is installed, you'll need a gem called log4r. Use the following command:
# gem install log4r
Once those two steps are out of the way, you're ready to download pmatch. Head to the project's Web site, and save the tarball to your hard drive. For some reason, none of my GUI archive tools liked the tarball, so open a terminal to the directory it sits in, and enter the command:
$ tar -jxf pmatch_0.2.tar.bz2
From here, pmatch is ready to use, but only locally via the command ./pmatch. To install pmatch system-wide, enter the following two commands:
# cp pmatch /usr/local/bin/ # chmod 755 /usr/local/bin/pmatch
From here, any user should be able to use pmatch at any time.
To use pmatch in its basic form, enter the command pmatch followed by the directory you want to examine. As an example, after doing so, I received the following shell output:
nhoj@ubuntu:~$ pmatch musostuff/storm-day/ rm musostuff/storm-day//verse2/raw-drums.wav rm musostuff/storm-day//sessions/steve-17-06-06/verse-drum-track.wav rm musostuff/storm-day//sessions/nhoj-session-26-2-06/session2.wav rm musostuff/storm-day//sessions/nhoj-session-26-2-06/session1.wav
Don't freak out when you see an rm followed by a filename. These are purely recommendations for the moment. If you actually want to perform these changes, you can do so by piping the command through to bash, like so:
$ pmatch musostuff/storm-day/ | bash
Now these commands actually will execute and remove said files. For more advanced usage and information on how pmatch works, check the Usage section of the Perfect Match home page.
Overall, this is a handy little project, which probably will make it into many users' toolkits and hopefully into distro archives. Once the project has fully matured, I wouldn't be surprised to see some GUI front ends making their way to our desktops.
I thought I'd finish this article with what has to be one of the quirkiest and most colorful projects I've come across—FpcBol. A desktop for children, FpcBol (or bol for short) is designed to be colorful and easy to use, with icons only (no menus), along with parental controls, and it's trim enough to work on older PCs. That all sounds cool, and some of it we've seen before, but the desktop and interface are the strangest I've come across and unlike anything I've used before—not necessarily a bad thing! Are you as intrigued as I was? Follow me....
First things first, the installation side of things is unfinished and in a state of flux. Florence Mathias (the project maintainer) and I were actually working together in a way on this one. He was changing the installation scripts daily while I gave him feedback. I thoroughly recommend checking out the How-To section on the project's Web site (itself simply a collection of colorful pictures and screenshots). With bol being based on Free Pascal and SDL, there are a number of obscure requirements and the How-To section has pictorial instructions of steps to take on individual distributions.
When you're ready to download the source tarball, click on the FpcBol picture on the Web site, which will take you to the SourceForge page's file archive. Once downloaded, extract the tarball, and open a terminal in the new directory. To any users of Debian-based systems, such as Ubuntu, MEPIS and so on, I thoroughly recommend running the install_debian script—it downloads all of the needed dependencies and will save you a great deal of frustration:
To start the installation, use the self-proclaimed ugly install script as follows (as root or sudo):
The script will go through a series of dependency and configuration checks. To start, it will see if you have something called bol.icone and download the latest for you if you don't (you won't, unless you've been through this process before). This is about 20MB, so go make a cup of tea and come back again.
A tricky error that probably will come up is a message saying:
jedi-sdl not present untar sdl.tar.gz (tar xvfz sdl.tar.gz) under /usr/lib/fpc/<version>/units/<cpu>/sdl
Look in the sources directory of bol, and you'll find a file called sdl.tar.bz. As root, copy it to your needed directory (/usr/lib/fpc/2.0.4/units/i386-linux in my case), change to that directory and extract the archive. Rerun the install script, and you should make it past this stage. If not, check that you have extracted sdl.tar.bz to the right directory.
If you receive the error, “Xmuu library not present !!!!!”, check your local file /etc/ld.so.conf to make sure it has the following lines:
/lib /usr/lib /usr/local/lib /usr/X11/lib
If these areas have all passed, a lovely little part of the program pops up with a spinning cube to test whether certain parts of bol will work in advance. Click on the small cube, and answer Y if it worked. If not, you're probably missing some needed libraries. After this, the script will ask you for the path to your mail reader and provide an example path for you. Enter the path for your favored mail application, and this should be the end of the script. Note that a script to install local configuration files for individual users is also provided. If you want to do this to make the first run cleaner, run the script by entering the following:
Phew! That was a long one, but a cleaned-up installer is on the to-do list for this project and may well be perfected by the time you read this. Some instructions are provided in the script, along with README files on how to integrate bol into your login menu, but I'll let you read that yourself.
You can fire this up straightaway on top of another desktop, so let's go through that for now, and you can take it from there. Open a terminal, and enter:
A bunch of initialization info will pass through the terminal before you're suddenly greeted by a crazy rotating cube in full-screen. I think this may be some kind of loading screen (I don't know), but the cube is cool. After a few seconds, your desktop will start changing, with a new background and a translucent rectangle (the workbench) at the top of your screen. The workbench is the part that drives bol, so let's concentrate on that.
The lower icons are application buttons. Hover your mouse over them, and they'll do a cool animation, and the name of the application will appear at the top of the workbench. Left-clicking on it will launch it. The heart icon represents favorites. Clicking it will change the lower icons to a favorite applications list. If you want to clear up your screen from clutter, the icon fifth from the right will show only the desktop and minimize everything else. What's the important button? Click the blue one with a question mark, third from the right—it's the help button! Your screen will suddenly be taken over by an assortment of writing and colors—it was so crazy I had to take a screenshot.
When you've had enough, double-click the red button on the right, and a confirmation screen will take over the workbench, telling you to right-click to exit (you'll see what I mean). Upon exiting the desktop, you'll be greeted by the cube again, but this time in reverse...groovy!
FpcBol is one of the craziest projects I've seen in a while. Its lack of menus may appeal to noncomputer-literate users. The graphical intensity will appeal to children, with moving icons, gorgeous colors and changing desktop backgrounds of interesting scenery. All in all, everything is gorgeous-looking and very...French! Kids will love it. The end result is definitely worth it, even if the installer is cumbersome at times. At the time of this writing, FpcBol just hit 1.0 alpha, and it may hit full release by the time this prints. Florence could do with a hand to complete things, particularly with improving the English and the installation scripting, so if any coders out there are fond of the project, why not help him out? There also isn't much documentation for the GUI and some of the cooler aspects like Parental Control and its log files, so I'd be keen to see how FpcBol turns out after gaining a decent audience.
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!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
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