Cooking with Linux - Browsers with the Speed of Lightning
Speed of lightning, power of thunder? What is this I hear? Mon Dieu, François! How on earth did you find that old Underdog clip? Ah, of course—YouTube. I am surprised, mon ami that you even know about this old cartoon—one, I confess, I enjoyed a great deal in my youth. Quoi? You don't know it? You were just doing some research for the issue's theme, underdogs? To be honest, I'm not exactly sure what our editors meant, but I don't think rescuing Sweet Polly Purebred from the evil Simon Bar Sinister was what they had in mind. Underdogs, François, refer to people (or animals or things) who are disadvantaged in some way. They may be smaller and not quite as strong as their opponent, so that in a contest or fight, they are expected to lose. People love to see the underdog win. But enough of this, François. Our guests are arriving as we speak.
Welcome once again, mes amis, to Chez Marcel, where fine wine is a naturally perfect match for fine Linux and open-source software. Please, take your seats and make yourselves comfortable while my faithful waiter attends to the wine. François, please head down to the cellar and bring back that 2006 Torbreck Barossa Valley Woodcutter's Shiraz we were, uhm, submitting to quality control earlier today.
Before you arrived, François and I were discussing the meaning of the word underdog. Cartoon characters aside, in the desktop Web browser world, you will find some true underdogs. I'm not talking about Firefox, and I'm sure most people no longer see Firefox as an underdog when compared to the Redmond OS's flagship browser. Instead, I want to show you some Web browsers worthy of the underdog label that you may well want to consider using. Despite not being as feature-rich as the heavyweights, these lightweight browsers have small memory footprints, make few demands on system resources and are, in many cases, as fast as lightning. Let me start with a text-only browser that, strangely enough, does graphics.
Links, created by Mikulas Patocka, is a text-only Web browser that is surprisingly rich in features (Figure 1). It can display tables and frames, and it supports colors, clickable links, SSL pages, background downloads and more. Sure, it works in text, but you have never seen pages load as quickly as you will when you decide to view the World Wide Web the way many of us first saw it—sans pictures. People doing research who want uncluttered information need to put away their graphical browsers and fire up Links. The effect of seeing only what you need, loaded in an instant, is a wonderful experience. Once you have used it, you always will make sure it is loaded on every Linux distribution you run.
Links' popularity means you don't have to look far for it. Most distributions have it in their repositories. Source is, of course, available from links.sourceforge.net.
Although it's true that Links is a text browser, it does respond to mouse clicks. In a nongraphical environment, you navigate by using cursor keys, jump from link to link with the Tab key, page using the spacebar and follow a link by pressing Enter. In a text console running under a graphical desktop, things are a little different. When you see a link, simply click, and you will go there.
Did I say text-only? I may have been mistaken. Graphically speaking, Links isn't merely a text browser. An update to Links, available from Twibright labs at links.twibright.com, provides a graphical interface that works even if you aren't running a graphical desktop. That's right. This Links will work on your framebuffer console as well (Figure 2). Once again, you should have no trouble finding the package in your repositories. The difference is in the command. To run the text-only version of Links, use the command links. For a graphical version of Links, try links-graphic.
Ah, François, you have returned. Please pour for our guests. Enjoy, mes amis. This Shiraz has a wonderfully rich aroma, complexity and texture, along with black cherry draped over the signature Shiraz peppery flavor. Make sure you fill my glass as well, François.
Another alternative to the monster browsers of today, and one that is entirely graphical in nature, is Dillo. Created by Jorge Arellano Cid, Dillo's demands on your system are meager, and its performance is seriously snappy. It won't render complex pages or tables particularly well, but it does support image browsing and bookmarks. Dillo's small size, speed and tiny memory footprint can sometimes make up for its limited features. Figure 3 shows Dillo in action.
The current 0.8 branch of Dillo is no longer maintained, but it's still a mainstay in most major distributions' repositories. It's easy to find and install. A new version based on FLTK2 is where development is going at this stage. Those of you feeling a little brave and willing to do a little source code compiling are invited to download the development code from the site at www.dillo.org. The classic source is also available.
Finding a balance between the needs of offering a feature-rich browser while maintaining speed at a maximum and resources at a minimum is the driving force behind the final two items on tonight's menu.
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)
- Tech Tip: Really Simple HTTP Server with Python
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Returning Values from Bash Functions
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Google's SwiftShader 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