Fun and Fame
Since 1994, Linux Journal has been demonstrating how Linux can be used to solve many problems. Much of the information presented has been in the form of either a HOWTO or documentation of a solution that has been implemented. This is certainly important, but it also seems important that we take an active role in bringing new Linux-based solutions to the world.
We tossed around a few ideas and decided that we could best contribute to this effort by presenting an idea and letting our readers turn it into a design specification. We would then select the best design specification from the entries we receive, publish it and help make the implementation possible.
We hope so. At the design stage, we will commit $2,500 (US) in prize money. We expect to award all $2,500 to a single participant, but in the case of similar designs or if the best design comes from combining multiple submissions, we will divide the money.
Once the design is complete, we will help move the process into the implementation phase. It's possible that we might have a funding source already established before we publish the initial idea. If not, we may use one of the existing open-source development marketplaces to establish funding.
The important thing here is that the design and implementation be open source. Our definition of open source is a practical one, not a nit-picking one. We want software to be released in such a way that it will do the most possible good, and that means that it should meet every possible contributor's definition of ``free'' or ``open source'' or ``freely redistributable''. So we ask that all code be released with a license that is listed under both ``GPL-Compatible, Free Software Licenses'' on the Free Software Foundation site (http://www.fsf.org) and also ``The Approved Licenses'' on the Open Source Initiative (OSI) site (http://opensource.org/). This means anyone can be a player in the long-term for the project. For those not familiar with this sort of development model, here are where the paybacks come in:
The design we have already addressed. We pay for it because we consider it a good investment that will help the community grow.
Development can be funded from multiple sources. If the product is of interest to multiple companies, then each should be willing to commit development dollars. While they will not receive exclusive rights to the implementation, they will get the system they want at a lower price than if they had to finance the whole project themselves.
If hardware is involved, companies can make their regular profit from sales of hardware. If the hardware is custom, this is a good chance for open-market competition to drive down end-user cost.
On-going support, bug fixes and continuing development can be done on a contract basis. While the developer has an advantage here, anyone can get in on the act because of the nonproprietary nature of development. This also makes it possible for a single company to offer complete support (hardware, software, training and support) for the entire system--something that many customers will require.
Embedded Linux Journal will continue to follow projects to completion. After completion, we will supply links to suppliers of the completed project, including support.
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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- 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
- SourceClear Open
- 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