Beachhead - Sinking of the USS Proprietary
I hang out at the small bar and restaurant called Alideia dos Piratas (Village of the Pirates) on my favorite beach. The owners are the Fafa Brothers, Jose and Chuy, and I regularly meet there to have dinner and discuss things with my friends, collectively known as The Dudes.
One day while I was having one of my favorite drinks, one of the Dudes came in very excited and told us that the latest victim of the sea, the USS Proprietary, was floundering offshore. Most of the people in the bar were not surprised. We had been expecting something like this for a while.
“Stupid people”, said Dennis, one of the head Dudes. “We told them that the ship was too big and clumsy for the shallow waters. It was not able to turn in time and got caught on the shoals. They should have had a smaller, more nimble ship sail into the harbor.”
I patiently explained to Dennis the economics of building ever-larger ships that could more efficiently carry ever-larger cargoes of goods, but he was unconvinced.
“Yes”, he said, “I understand the issues, but think about the fact that larger ships can go only to the larger ports. Then you have to pay more to ship the goods to the areas where you really want them. Smaller ships can go closer to the other towns and reduce the overland transportation time and costs. You give up flexibility when you use the 'bigger is better' strategy.”
Some of the other Dudes started chiming in. “Yes”, said Jimmy, “and I wanted to ship just a small desk the other day. If I wanted to send it via one of the big vessels, they wanted me to 'consolidate' it with other items, and would not talk to me unless I needed to ship tons of cargo at one time. It would have taken me months of time to find enough furniture to make the large shippers even notice me. The smaller ship captains were eager to get my business, and I got my desk shipped in the time frame needed for my customer. So who gave me better service, the large ship or the smaller boat? I could not even get the proper telephone number for the larger shipper—I just kept being put on hold.”
“What about risk?”, I asked. “Don't you feel better about relying on the larger firms with the bigger boats?” Thiago snorted, “And what ship is lying offshore floundering? When I go to try to get restitution for my lost goods, whose throat can I get my hands around? Have you ever really read their warranties and liability limitations? I know where to find the small ship captains—they usually go to my church, my club and are on my Chamber of Commerce. They are local to me and value my business. The money I give them to ship my goods stays in the local economy, and often they come to my shop to buy food. When I give money to the owners of Proprietary, they take the money out of the local economy and I never see it again. It may even go out of the country, affecting our balance of payments.” Thiago always was the deep thinker of the group.
It was now Chico's turn to add his thoughts, “What about the 'shipping drain'?” We all turned to him with a quizzical look. “Sure”, he said, “we train lots of people in how to sail ships, but then they leave the area and go off to find jobs on these big ships. We lose the best people because they do not feel they can get a good job locally. If we could make it easier for them to get a decent living here, they would stay here and build up the shipping industry again. Remember, 'Think globally, ship locally.'”
“But guys”, I said, “surely there are jobs that are just too big for a bunch of small- to medium-sized ships to tackle. Jobs that require something the size of the USS Proprietary.” “Maybe”, Dennis agreed, “but you really should think about it and balance the issues. Most of the time the smaller vessels would be just fine, and other times you might be able to break up your shipment to take advantage of the greater flexibility of having smaller boats, rather than having to put all of your shipment on one carrier. This is just one of the advantages of having control over your shipment, instead of relying on a consolidator who puts everything into one black box and refuses to let you exercise control.”
With that we all stared out to sea, looking at the other hulks of boats lying on the shoals, whose cargoes went down never to be recovered:
And we wondered when the Proprietary would have its final death knell.
Jon “maddog” Hall is the Executive Director of Linux International (www.li.org), a nonprofit association of end users who wish to support and promote the Linux operating system. During his career in commercial computing, which started in 1969, Mr Hall has been a programmer, systems designer, systems administrator, product manager, technical marketing manager and educator. He has worked for such companies as Western Electric Corporation, Aetna Life and Casualty, Bell Laboratories, Digital Equipment Corporation, VA Linux Systems and SGI. He is now an independent consultant in Free and Open Source Software (FOSS) Business and Technical issues.
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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Rogue Wave Software's Zend Server
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