Enterprise: Linux, Starships and Postscripts
Always playing with the semantics of each issue's focus, Marcel Gagné reminds us that for many, the word enterprise conjures up visions of Captain Kirk and the starship under his command. But by Captain Kirk's time, the name Enterprise (sometimes Enterprize) was already an old one for warships. A 12-gun US naval schooner built in 1799, the third US naval vessel to bear the name, is perhaps the most famous (next to the starship, of course). It was this little ship that spawned the tradition of passing the famous name to innovative or “enterprising” ships in the 20th century (i.e., a WWII aircraft carrier and the first nuclear-powered aircraft carrier). The schooner served with distinction through the engagements with the Barbary corsairs, the Quasi War with France and the War of 1812. She was commanded by some of the most notable names in US naval history, such as Stephan Decatur, Isaac Hull and James Lawrence (of “Don't give up the ship” fame). Michael Bosworth writes that “Enterprize, in her original schooner rig, had a reputation of being fast, and she was remarkably lucky in her assignments, her timely refits and her officers and crew.” When the time came in 1803 to build more naval schooners, it was hoped that the Enterprize could serve as a model. But alas, no Enterprize plans were to be found, and the schooner, while lucky in her own right, could not be reproduced. Her career was a collection of serendipitous and fortuitous events that entice one to believe she was fated to succeed.
Despite the hard work of thousands, the point where Linux now sits can similarly be considered a lucky or fated enterprise, especially when one considers the role initially played in that success simply by the personality of Linus Torvalds. But now Linux seems to be at a juncture. The initial hype and excitement are gone, the bandwagon jumpers-on are gone, and it's time to see whether Linux can continue its maturation rate and present a viable solution to an ever-increasing variety of applications.
While it's important not to forget the many improvements yet to be made to Linux, I like the attitude in David Bandel's column this month—that the existence of many large companies using Linux is proof that it is ready for the enterprise. Our article on Bike Friday and their move from Microsoft to Linux supports this, and this month's Linux Bytes Other Markets highlighting a manufacturing firm that uses Linux for everything, including every employee's desktop, is another drop in the bucket of evidence that this player is ready for prime time.
As a side note, plans for a ship believed to be the schooner Enterprise were recently found in Venice. The plans are being used to construct a replica in Washington, DC that will be used as an educational ship and goodwill ambassador.
Richard Vernon is editor in chief of Linux Journal. He enjoys studying naval history and really knows his way around a dinghy.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
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