The Penguin Driven Church Office
We use Linux for general use, mostly as a desktop workstation. We use OpenOffice.org (OOo) and Mozilla for Web browsing and e-mail. We are developing our own church management system, using MySQL and PHP. For the time being, we manage our data on a spreadsheet. But, we're looking to the future, when we'll have a need to move our data into a real database.
OpenOffice.org offers some serious advantages over other office suites. We can connect directly to a variety of database servers to retrieve our data into Calc, the spreadsheet feature, or Writer. If we want, we then can export that data to Adobe Acrobat's PDF format. Data storage is not a big deal these days, but my Writer documents are a good bit smaller than their proprietary equivalents.
Mozilla's Web browser offers tabbed browsing. Ever since I experienced Quarterdeck Mosaic, I have prayed for tabbed browsing. Mozilla and its variants offer it; probably most Linux browsers offer tabbed browsing, I'm not sure. You can check your e-mail and newsgroups with the e-mail client. You even can build your Web site using the Composer. That's great for users who don't know much about HTML.
I mentioned that we're developing our own church management system. Look, I'm not a programmer, which is why I'm learning as I go. Info Central is one available application, but we've chosen to do it ourselves. Again, multiple factors are involved in this decision. None is more important, however, than the learning experience.
Because we are in the midst of launching a computer training program, we need to be able to teach skills to which people otherwise may not have access. At some point in the future, we'll be able to offer database administration and development classes. And the skills students learn will be usable across various platforms. This leads us to the next phase of our ministry--education.
The KDE desktop offers some educational tools that we can use to help young people or even our members. Using KEduca, we can develop a Bible trivia quiz for our members or test preparation lessons for school students. We can offer typing classes or teach geometry, foreign language vocabulary and even astronomy. Scilab offers stuff that only a high-school calculus student could love.
Linux includes numerous games. Our church could run tournaments for chess, backgammon, Scrabble and several card games--all over a small network. These are only some of the nifty things a little church like ours can accomplish using $80 worth of software. That's right, we spent $80 for all of this. That's stewardship.
Just as the faithful turn to the scriptures to help them solve life's problems, so too, Linux users have helpful resources available to them. Man and info pages offer help with commands. How-tos offer the more conventional step-by-step instructions for particular tasks. SuSE and most other distributions include additional help documents specific to their distribution.
If you cannot solve your problem that way, there's always the e-mail lists, news groups and Web site bulletin boards. Linux support sites, such as LinuxCare, offer commercial support. Linux Support Services offers free assistance. Additionally, the commercial vendors offer technical support and usually include some sort of Web support as well.
Is it right to let a penguin into your organization? Only your organization can answer that. For us, it was a matter of me deciding we would use Linux. For most church leaders, though, it won't be that easy. Many have church boards to answer to, an office staff that will get stuck with the end result and that special someone who objects to everything but singing "Amazing Grace". Therefore, time will be spent hashing out the reasons for making a change--or, for newer churches--starting out with Linux. I hope the reasons for using Linux are now clear.
So what about the reasons for changing? The reasons commonly given for using proprietary software often reveal more about our biases than about the facts. I've taken the liberty of helping you reason through some of the arguments you'll hear in favor of your current legacy system.
The old "Everyone uses Brand X" argument doesn't hold water. I already have said that open-source software is highly compatible with many proprietary products. The notion that legacy software is easier to use than current open-source products is not always true. Installing my HP 970Cse duplexing printer was much easier with Linux than with the proprietary system it replaced.
Many people tell me what they've heard about Linux, often quoting some IT expert from their workplace. The problem is that these IT experts may or may not have used Linux. They may be answering from the perspective of their companies. They simply may think that your users are too dumb to use Linux--an insult to your intelligence. Effectively, many get what they ask for, an opinion. That opinion may not apply to your situation.
Consider this. I know IT experts who don't know much about Linux. Meanwhile, I've been using it since 2000. They know only what they've read about Linux. One guy has a copy that he hasn't installed yet. When I discuss certain network services, he's lost. These are well educated, very experienced people. They simply don't know Linux well enough to make a claim about it. Hence, their opinion cannot be taken as an in-depth analysis for using Linux in our church.
If you're going to ask an IT expert to help you make a decision about Linux, make sure he or she has at least some experience with Linux. That expert's thorough understanding of your situation will affect the final analysis. The expert needs to have an understanding of your current skill set, your attitudes toward change and your current hardware and software situation.
Churches can launch a computer ministry, effectively creating a group of members who undertake to learn Linux over a specified period of time. The group members could use their own computers or a single computer dedicated to this mission. This group also could work with other churches in a combined effort and then lead your church through the migration process.
To aid you in presenting your case, you should demonstrate Linux for the folks who will be using your system. Invite the local Linux Users Group (LUG) to show off Linux for you. Alternatively, many distributions offer evaluation CDs that don't have to be installed to run. If nothing else, designate a team to get a boxed distribution and play with it on a single computer. They can run the demonstration for the others.
I think the demonstration is going to be important for the doubting Thomases in your midst. People need to see the differences and similarities between Linux and whatever operating system they currently use. You even could set up a single system that everyone can play with for a few weeks. Your more adventurous types may not need that, but the timid folks will appreciate it.
When it comes to data, churches need to consider their options carefully. A new church with no significant data is an ideal candidate. A small church using a legacy operating system and legacy office software could migrate easily in short order. Larger churches, with a lot of data stored in a proprietary application, need to consider a gradual migration.
Although most applications do allow you to export your data to a standard text format, some may require specialized tools. Even though you may feel trapped in your current environment, all is not lost. Simply deploy Linux on a limited number of PCs in your office until you develop the ability to migrate all your data to one of the databases included in Linux. Again, you've got options.
Once you export your data to a standard text format, such as the tab-separated values format, many Linux applications can work with your data. You can set up tables in MySQL to match the columns in your files. Then, simply load the data into the database with a simple command, and you're back up and running. Well, there is more to it than that. But at least you get the general idea, and that it it's fairly simple and straightforward to accomplish.
There is one more option for using Linux in your organization: running Linux with other operating systems, such as Windows or OS X. Linux plays well with other systems. Many businesses are using the mixed or hybrid approach to prevent getting trapped with software that they don't want. That way, you can run your legacy software while taking advantage of the many powerful features Linux offers.
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|
- The Firebird Project's Firebird Relational Database
- Stunnel Security for Oracle
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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