Open Source POS Project
This project is to create an open-source Point of Sale (POS) system. While we are just starting this effort, I envision that it will build a set of tools that can be assembled and customized to address a variety of POS requirements. If we do our job right, VARs will select these tools as the basis of their solutions, and some of us may even go on to be VARs ourselves. In any case, getting VARs to select a Linux-based solution is the goal.
What are the tools I am talking about? There is an amazing array here. On the geek end are drivers for barcode readers, touch screens, IR devices and such. On the business end there will need to be accounting software and reports. In each case we need to identify what is needed, design and build the tool and get it accepted by vendors outside the Linux community--be they hardware manufacturers or service providers such as credit card processors.
Many of these pieces already exist--our effort will be to get them working together and documented. Others will have to be written. Ultimately, we will have a complete tool kit with documentation that can be used to build precisely what the customer wants. This customization ability can be a big win over solutions based on closed-source software.
We have just started a mailing list to discuss the effort. If you want to join, send e-mail to firstname.lastname@example.org and put the line subscribe opos-list in the body of the message.
This project was inspired by some questions on the Free Software Business mailing list run by Russ Nelson. I have many years of experience in embedded systems with a few years developing POS systems for the fueling and convenience store market. Dan Wilder, also on the SSC team has over 15 years of experience in POS systems. We want to bring our expertise to this Linux-based effort.
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!
- Google's SwiftShader Released
- Interview with Patrick Volkerding
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Returning Values from Bash Functions
- Managing Linux Using Puppet
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