On the Web - Toward an Open-Source Government
Many people in the Open Source community have long believed that open-source software and the government are a good match. As any state-level politician can verify, US state governments are faced with the worst budget conditions in at least 50 years. In addition to having to gut and cut programs and services possibly needed by more people than ever, many schools and state-funded universities are expected to provide more technology for more students with the same or less money. In light of these conditions, some proponents of open source believe now is a perfect opportunity for states to save money by moving legacy systems to and creating new systems that run on open-source software. It's no longer a maybe, someday thing, if it's a small and adventuresome state agency.
Getting governments to make these switches, however, is where logic and progress can hit a wall of regulation, procedure and red tape. State and local governments seem to be the best place to start the move for change, so if we're going to give it a shot, we better know what the current procedures are. To that end, Tom Adelstein has been writing a weekly series for the Linux Journal Web site that covers the current state of open-source in government. “Linux Access in State and Local Government, Part I”, /article/6927, reviews specific states' endeavors to legislate consideration of open-source software and details some of the detours these endeavors encounter. In Parts II and III, /article/6952 and /article/6970, Tom covers particular state agencies in Texas and Oregon and explains where they were successful in using open source and where they were not. Finally, in Part IV, /article/6990, Tom walks us through the process of getting IT legislation through state government.
In a similar vein, Joe Barr's article, “Austin, Texas to Begin Linux Pilot Project”, /article/6974, describes how the IT department for the city of Austin is launching a city-wide program to use Linux desktops, servers and thin clients. The city's new CIO is “especially interested in seeing what sort of performance and savings he can get out of running office applications on a server with terminals as the desktop”. If cities and states can get out from under some of the proprietary licensing fees and TCO, perhaps more money will be available for all those national defense and antiterrorism programs that states are supposed to enact without extra national funding.
Moving on to something a little lighter, here's your project for the month. Use Jeffrey Taylor's “Peering Over the Firewall” how-to (/article/6985), Snort, a custom cable and an Ethernet hub to build your own low-cost intrusion detection system. By the end of the project, the Linux box will be the firewall and router in your home network, and you'll still be able to peer around the router and see all incoming packets.
If you have an open-source-in-government story or a do-it-yourself project you'd like to share, send your proposal to firstname.lastname@example.org. Be sure to check the Linux Journal Web site often; new articles are added daily.
Heather Mead is senior editor of Linux Journal.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 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