Caldera, Inc. recently made a move to focus itself better on two product areas. The intent was to create two wholly-owned subsidiaries to address Caldera's two target markets. What are those markets? The one we know is Linux, the other is the Embedded OEM (original equipment manufacturer) market, where they offer DR-DOS.
On the DR-DOS side, the new company is named Caldera Thin Clients, Inc. Linux folks care because this is a market in which Caldera competes with Microsoft's Windows CE. Offering DR-DOS-based solutions makes for more compact solutions for the developers, and also shows that an Open Source alternative can make it in a non-Linux market.
On the Linux side of the house, the new company is named Caldera Systems, Inc. Ransom Love is President and CEO of this company and Dean Taylor is Director of Marketing. Bryan Sparks, who will remain President and CEO of Caldera, Inc. said, “The ever-increasing popularity of Linux-based solutions for business encourages us to create a company solely focused on these opportunities.”
To me, this move makes sense. Both subsidiaries are pursuing non-Microsoft computing solutions, but they are in different directions. DR-DOS is being offered as an embedded solution. As it is quite small, it can fit the needs of the low-end embedded market which includes such devices as digital cameras.
Linux solutions, particularly those for business, which is Caldera's focus, require a totally different approach. To be a business success, you need to offer a complete solution. In one market, this could be Linux configured in a particular way to act, for example, as a router or firewall. On the more complicated end, we could be talking web server, database and web development software or a vertical application such as a system designed to run a dentist's office.
The types of marketing and support for these two markets are quite different. By splitting into two subsidiaries, it will be much easier for Caldera to follow the needs of the markets and form the necessary alliances to make things happen. I expect to hear more about this in the near future.
In Pacific Beach, Washington, there is an event called Kelper's Weekend. Last year we entered the parade with my old Mercedes and a computer attached to its roof. This year we went one better. The theme was “Linux Invades Pacific Beach”. Our entry included my electric car decorated with glitter, an alien on the roof and even an alien driving it. The word LINUX was prominently displayed on three sides of the car. Besides the car, we had a motorcycle driven by a penguin and a host of SSC employees and friends in Linux T-shirts handing out candy and toys.
Although one naysayer championed Microsoft as the car passed, it was noted that once again that software giant was not represented in the parade. On Monday, The Daily World, the only daily newspaper in the area, had a photo of the Linux alien car and motorcycle penguin on the front page. It was nice to see good press coverage of our operating system here in Washington state.
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
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- 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