Linux Access in State and Local Government, Part I
People believe that governments have embraced Linux and open-source software. You might see headlines saying that Linux advocates have made serious inroads in government. Logic dictates that Linux works well and the price is right, so why not?
This year, Oregon and Texas legislators introduced house and senate bills respectively supporting open-source software. Both legislative bills made their way to committee hearings, but the results differed significantly. Oregon's HB 2892 died. In Texas, SB 1579 found favor in the Committee and remains pending due to a walkout by approximately 50 members of the House.
California and Oklahoma also made attempts do some legislative mandating to use open-source software that died quietly. Rhode Island didn't see legislative action, but it did build a Linux portal for the state's rules and regulations database, which received good reviews.
Other states, such as Alabama, attempted grass roots efforts from their Information Service Departments to implement open-source initiatives. Grass roots efforts exist in Iowa, Utah, Hawaii and Louisiana.
We discovered open-source initiatives in city and county government units across the country. Similar to commercial users of Linux, the various local efforts have started at the bottom. One city in a far northwestern state secretly deployed Linux to avoid an entanglement with a local software company. In Texas, Houston looks like a pioneer and has already seen reduced costs and saved taxpayer money.
Depending on your worldview, we could say the Open Source community made important strides or failed miserably in the past year. Regardless, we gained extensive knowledge of our situation in state and local government. This discussion covers specifics of our overall findings.
The main thing a government unit considering open-source software wants to know is how it can save money. The people who answer to their constituents need to show cost cutting and a balanced budget.
A level below the legislators and government officials lays a large, permanent bureaucracy. The managers spend time working on technical issues such as reliability, continuity, security and interoperability. At lower levels, people maintain the existing systems with little funding for development. They need solutions they can deploy with little effort that fit seamlessly into their infrastructures.
Interested parties make up the final group with issues. These include advocates and the opposition. Here, I depict the opposition as well funded and organized. The advocates have little organization, financial resources and/or participants.
During the Texas hearing, Senate sponsor John Carona summed up the money situation nicely during the hearing before the Administrative Committee. He addressed the lobbyists making up the opposition and said:
Again, I don't understand why you all are so threatened by this, but from a careful look at the lobbyists in this room that are representing Microsoft, and all of you here representing proprietary software companies which—let's face it, that's where the big money is; it's not in open source, it's in proprietary—it's rather transparent as to why you all feel so threatened by this language. And I'll tell you, this [bill] is innocuous, but next session I'll be on a crusade.
Elected officials and state bureaucracies have little agility in the area of information technology budgets. Meanwhile, lobbyists and the popular press continue to say that open-source software provides little, if any cost savings. Analysts, such as Andrew Binstock of Pacific Data Works LLC, say governments are conservative when it comes to new technology.
Rhode Island became the first state government to implement open-source technology in view of the public. Jim Willis, the special project consultant for the Secretary of State, chose open-source software to implement an on-line rules and regulations database. The implementation used LAMP, which stands for the Linux operating system, Apache Web server, MySQL database and any of three development languages—PHP, Perl or Python.
The state developed the database-driven portal for $40,000. Hardware costs amounted to $6,000. Deployment cost $3,000, and the remaining funds went for overhead and one consultant working only two days a week for four months. The portal runs under Red Hat Linux 7.2 and sits on a Dell PowerEdge server that came with a MySQL database pre-installed. Ninety-five agencies use the portal to submit PDF files with information on rules and regulations to the Secretary of State's office. The database currently holds approximately 1,700 regulations.
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
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SourceClear Open
- SuperTuxKart 0.9.2 Released
- 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