Technology

The Church is not a business, though some aspects of business experience are helpful when managing earthly aspects of the Church.

Because of that, a Christian congregation is also not a business. Likewise, a synod or larger church body is not a business.

The business world is a bit like the military world. Decisions are made by a few, and everyone else has to follow them. Dissent is not tolerated. The leader(s) determine the principles of the organization, and anyone who contradicts them is terminated or disciplined.

This has been extended to publications. If an employee writes a book or blog that somehow comes against the principles or interests of his company, then he is in trouble. His allegiance, even in his privately published writings, is to his company. Personally, I think some companies have taken this way too far, but it's a free country. They have the right to be wrong, just like the rest of us.

In the Church, our primary allegiance is not to our own congregation, nor to our synod, per se. That would be a kind of idolatry. It would be denominationalism, like backing the Red Sox only because you live near Boston, rather than because they have any particular virtue or skill. Applied to baseball, that approach is fine. Applied to churches, it's wrong. Some churches and synods are more virtuous than others, because they hold to the Word of God in doctrine and practice better than others.

At one of the churches I serve, there is a Canon iR 2230 digital copier, called an "ImageRunner." It's a nice monochrome copier, especially nice for a small congregation. This one has a network interface, and can function as a network printer with Canon's proprietary UFRII printer language. Canon also reportedly offers a network interface that supports PCL, but I haven't had any success in getting one. It's probably expensive anyway.

For almost 2.5 years now, I've been trying to figure out how to print to the ir2230 from Linux, without success. There were drivers from some European web site that didn't work, and suggestions from a local tech to try drivers for similar machines --- that also didn't work.

Today, I did another search, and stumbled upon a Japanese web site that has drivers available for CUPS, in both rpm and debian packages. Holding my breath, I installed the debs. I can happily report that the CUPS test page printed flawlessly. The driver includes a PPD that uses Ghostscript to process the Postscript job before sending it. The driver seems to support duplexing, as well as collating, stapling, and hole punching. There's also a little GTK+ program for sending jobs through CUPS, which supports the device's features more explicitly.

The place to get that driver is here. Just scroll down until you see the links for RPMs or Debs.

I wonder how many people can decipher the title of this post. If you read or write a lot of documents typeset with LaTeX, then the formatting of this will look familiar. I happen to typeset nearly everything with LaTeX.

In other news, SCOTUS has confirmed what has seemed apparent to me for some time: the second amendment to the US Constitution (like the amendments in its immediate context) protects an individual right from infringement by the United States Federal government. Score one for federalism, and celebrate while you can.

If you're the sort of person who looks for the most efficient and satisfying ways to get the job done, regardless of the conventional wisdom, then read on. If you're the sort of person who conforms to the expectations of others, and believes that the most popular or the most widely adopted way of doing something is always the best way to do it, then you may as well stop reading now.

I am not one of the latter types. Your way of doing things might work fine, but it won't necessarily work best for me. I want the freedom to work my way.

That's why I like the Unix environment, and why I use Linux for just about everything. It fits me. I have the freedom to do things in the ways that work best.

For about ten years now, give or take, I've been using a collection of utilities and systems that provide the following important features:

• High quality desktop publishing with a high degree of automation. I'm not talking word processors here.

• An extremely efficient and powerful editing environment in which I rarely have to move my hands away from the home row of the keyboard, even when executing complex procedures using multiple programs, like importing some extracted Bible verses, or search results.

• Independent programs where each does a specific task in a predictable and efficient manner, which can be interconnected easily to perform complex functions, even from the comfort of my editing environment.

• Efficient archival of important changes to my work, so that mistakes can be reversed, old versions found, etc.

• Network access to all of this work, so that I can use the system equally well here at my primary computing location, or anywhere I have connectivity.

• Freedom and access to adjust the way I work in any way that I might see fit. (This may be the most important feature.)

• The ability to expand and augment the system with tools of my own creation.

I enjoy these and other important features in my daily work, because I use Linux (Debian GNU/Linux, to be precise), Vim, LaTeX, Python, Git, SSH, Mutt, Gimp, and a many other programs and projects, representing many thousands of programmer's hours. I also use programs I've written too, though they're not so famous.

If you know what Libronix is and does, you probably already know where it falls short in my view. The problem is not that I want to rip off lots of copyright holders and distribute their work indiscriminately by means of the Internet. The problem is that I want to use those copywritten works fairly, yet without being hamstrung by a computing environment that (a) doesn't give me the freedom and power I need, and (b) charges me a lot of money for my loss of freedom, power, and stability, too.

Unfortunately, the Windows environment is automatically disqualified. (Case in point: DRM is supposed to be a step forward for Vista. It's actually a big step backward for someone like me.) The constant upgrade cycle alone is too expensive, though I'm sure MS shareholders think it's great. I'm probably one of them, come to think of it.

I've enjoyed using the Macintosh environment, mostly because I can use the same Unix tools that work together so efficiently. The next time I have $2k I don't know what else to do with, I might just drop it on a Mac. Macs are just priced out of my league, and they have an expensive upgrade cycle of their own.

As for Libronix, I understand the philosophy: control. It's like the Matrix. All those snazzy features: searches, hyperlinks, notes, etc. --- it's all about control. The software is written that way in the hope that you never want to leave it. The proof of this is that you can't export works from the digital library. Oh, you can export tiny bits and pieces, but not whole works. So just leave Libronix running all the time, and you'll always have access to your digital library. Do you need to search? Just enter the Libronix application. Do you need to extract something? Switch over to the mighty Libronix app. It's your go-to guy for everything related to your digital library.

I'm sure the approach works. It's one way to do it. But sometimes it doesn't work. (It locked up on me more than once when running it in Windows 98 under VMWare.) It also takes a while to load and run. It also interfaces only with whatever editing environments the Libronix designers anticipate, and that their marketing model will support. In case you haven't guessed, that doesn't include Vim. It also can't be used remotely over SSH. And so on and so forth. Meanwhile, I'd like to grep through a UTF-8 file of Concordia: The Lutheran Confessions and get the results in my text editor, for possible use in my next Bible study. Something wrong with that?

Libronix probably works great as a money-maker for Logos, though I'm sure that's not their (only) purpose in producing it. Libronix probably does a good job of protecting the interests of copyright holders. It probably seems great to the great herds of computer users who don't care to look for "a better way to do it." But Libronix doesn't work for me.

So if you are a copyright holder wishing to publish your work digitally, consider those of us who don't appreciate being locked in to one vendor, even a vendor with good intentions. Frankly, I value freedom. I'll respect your copyright, but if you won't publish your work in a way that I can use it, then your hands are tied. Wouldn't you prefer that your work gets used?

And if you work for Logos, please consider a release for Linux that includes quick access to the digital library from the shell. I'd be happy to work with you on it.

If something seems different at The Plucked Chicken, I'd be surprised. But if it does, it's because I've upgraded and rearranged some things on the old home network.

It began when I wanted to install something on the server that hosts the PC. (I don't even remember what it was at this point!) For those who don't use a Debian-based flavor of Linux, I have to explain how most software installs and upgrades work. It's pretty easy. Software is split into packages by task, functionality, mutual compatibility, and versions. So the first step is to find the package you want to upgrade or install, and there are package-management tools that make this fairly easy. (Understand that there are somewhere over 6,000 Debian packages.) After that, you use one of several package-management tools to do the upgrade or install. The computer handles the rest: figuring out dependencies, downloading packages and installing them. It even checks cryptographic signatures when possible to make sure nothing insidious has happened.

So I tried installing something remotely on the server machine, but it had been a long time since I'd performed a major upgrade, and years more since I'd upgraded the Linux kernel. I just didn't want to mess with it, because it sits there, happily running connected only to 115v AC and 10Mb ethernet. Then, I messed with it. The installed system was quite outdated compared to current Debian systems, and it needed a new kernel.

Time past, I'd compile a new kernel without blinking. It was standard operating procedure for a long time while using Linux 2.2 and 2.4 kernels, and pretty easy. (I fondly remember a presentation Joe Abrahamson made to the LUG in Mankato on configuring a kernel for compiling.) This machine was still running 2.4, and Debian is now shipping with something like 2.6.20. I didn't like the prospect of a full kernel compile on that 333 Mhz machine, not really remembering exactly what hardware it contained. So tried a few short cuts and rebooted it remotely, fingers figuratively crossed. It didn't come back up. That was Friday morning.

Fast forward past a late night/early morning, one-man emergency computer rebuilding party, involving a GRUB emergency boot disk, a spare hard drive, a CD-ROM drive borrowed from the kids' room, a newly-burned Debian net-install disk, and an uncooperative DSL modem. As you can see, the PC is up again. Now it has more hard drive space than ever before, sporting its own CD-ROM drive (invaluable for emergency boot/install situations), and a brand-new hostname in honor of a fictional young man whose brief experience as a dragon changed his life for the better. It still has only two wires: 115v AC and now 100Mb ethernet (swapped with kids' computer).

I remember spending many late hours trying to get Windows or its programs to work. That was many years ago. It's inevitable, because computers are just complex machines. Even appliances go berserk from time to time. The frustrating thing for me was that I paid good money for the privilege of that sleepless (and often fruitless) wrestling to get things working properly. It was about that time that I tried some alternatives in the hope of finding a Better Way. That included OS2/Warp, and would have included MacOS too, if I could have afforded it. (MacOS 7 was current at the time.) Then, I learned about Linux. I reasoned: "Why pay for my problems, when I can have them all for free?" The surprising thing was that my problems and frustration were also dramatically reduced, while my productivity and satisfaction were dramatically increased. See? You get what you pay for.

Linux is still free, and my problems are still few. Now, though, you can buy low-cost computers running Linux from Wal-Mart and many other places. Also, many (most?) of the embedded devices you use without even realizing it are running Linux.

Just think: my recent upgrade adventure, which wasn't even so bad overall, used to be so commonplace that it was hardly worth writing about. Now, it's rare enough -- for me, anyway -- that I mentioned it on the Plucked Chicken. So thank you, all who contribute to Free Software!

In The Lutheran Hymnal and in the Book of Family Prayer there is a schedule of Bible texts that may be used for devotions through the Church Year. From what I can see, its chief advantage is variety. Its disadvantage is convenience. I find it much more convenient to keep a bookmark in the Bible that sits on our living room shelf. Then I can grab that Bible (or the second edition of Concordia that sits nearby) for something to read during breakfast.

In the Evangelical Lutheran Hymnary there is a list of the monthly psalter, which takes the reader through the entire book of Psalms once a month, with readings in the morning and evening. For a few years I had my computer sending out those readings via email. That worked well enough. Someone suggested that I make it available as an RSS feed instead. I never really had the right combination of opportunity, means, and motive, until today.

For a few weeks now, I've been producing a bulletin insert for my churches here containing some ideas and helps for use in personal devotion. Included are the readings from both the schedule I mentioned above and from the monthly psalter. That's also where I list prayer requests, Sunday school lesson themes, and progressive excerpts from the Small and Large Catechisms. It's a useful little insert, especially for those who can keep one handy through the week. I could do that, but today I realized I can do something else, too.

In the last year or two, I've been using an RSS feed aggregator to keep up with a few blogs and news sources. Right now, I'm very satisfied with one called Akregator, which is part of the KDE desktop environment. For those who don't know what an RSS feed or an aggregator is, here's a brief (3-paragraph) explanation:

Many web sites have pages or other information that gets updated from time to time. If you want to stay abreast of the information with your web browser, then you'll have to fire up your browser and tell it to show you that page every time you remember to check for changes. Sometimes, there will be no changes at all, so you will have wasted some time in checking. Sometimes you won't even remember to check for a while. That inconvenience and wasted time is solved by RSS feeds and aggregators.

An RSS feed can be provided by the web site you want to keep tabs on. It's a link that shows a machine-readable list of recent changes. Each item in the list of changes can contain a link to the changed information, a comment or description, a bit of audio or video media (then we call it a podcast), and any number of other useful tidbits.

An aggregator (or feed reader) is an inobtrusive program that you keep running on your computer, which periodically checks all the RSS feeds you may be interested in for new information. When it finds something new, it lets you know. The aggregator also provides a way for you to subscribe to new feeds, manage your feeds, and even view the items they contain. Google and other web portals have built-in aggregators, but I prefer one that I can use without a web browser.

So today I decided it's high time to provide this devotional information in an RSS Feed. Anyone can use it. Each item you fetch from the feed contains a brief description and a link to the devotion text for that time of that day. At 12 PM Pacific, the feed switches from morning devotions to evening devotions. (If you're in another time zone, there's not much I can do about it. I don't think I have access to your tz information when you fetch the feed.) Generally, there are two items in the feed: the devotion text and the psalter reading. Since there are no devotion texts for Sunday, the feed is set to provide Sunday texts from the historic lectionary.

If you already use an aggregator, or if your brower has one built-in, then all you need is the link. You can use either of these:

• http://www.bethanythedalles.org/devotions.py

• http://www.concordiahoodriver.org/devotions.py

If your web browser doesn't know what to do with those, and you don't have an aggregator, then I suggest that you try out some free ones. You'll find links from Wikipedia, among other places.

Nothing against those in the Windows world out there. The Matrix has you, and it's not really your fault.

I admit that I've been curious about Vista. The hype has been impressive. But then, it's still Microsoft Windows after all, isn't it? That explains this, from Bruce Schneier:

Windows Vista includes an array of "features" that you don't want. These features will make your computer less reliable and less secure. They'll make your computer less stable and run slower. They will cause technical support problems. They may even require you to upgrade some of your peripheral hardware and existing software. And these features won't do anything useful. In fact, they're working against you. They're digital rights management (DRM) features built into Vista at the behest of the entertainment industry.

For more information, take a gander at badvista, which led me to Schneier.

The last Windows PC I ran was Windows 95. I had my fill. Since then, I've used virtual hardware to run my (ancient, legal) copies of Windows only for testing, debugging, and mostly tax software. As far as I know, they still haven't released TurboTax or TaxCut for Linux yet. At least it's available for MacOS.

If you have the means -- which is measured in willingness to learn rather than dollars -- there has never been a better time to try Linux. Ubuntu is hugely popular, and is rather easy to install. Its variant Kubuntu is even prettier (IMO). For those who absolutely must spend money on an OS, look no further than the Macintosh. It does what you need, and in general it's not broken.

Bruce, at Pagans and Lutherans, has expressed some necessary thoughts about something called "open source religion."

As an avid Open Source Software user, I have to add my own two cents. "Open Source" refers to the way software source code is treated. Source code is the human-readable programming code that is somehow translated into instructions that a computer is able to follow. Microsoft products have source code, but if someone like me wants to see it, I have to pay scads of money (as though they need more) and sign my life away first. Open Source (or "Free") software is different. Anyone can obtain the source code at nominal cost. What's more, anyone can use that source code to make new software, with only one major requirement: new programs that incorporate existing Free Software source code must themselves be Open Source. This guarantees that others can improve on Free Software that I write, and also that the source code of those improvements will always be available to me, in turn. For more information, check out the Free Software Foundation and the Open Source Initiative.

The Free Software movement has spawned an industry in competition with the likes of Microsoft, and in my opinion, destined to outlive Microsoft. All of the programs involved in my writing of this post, for example, are Free/Open Source Software (sometimes abbreviated FOSS). That includes the operating system, the desktop environment, the text editor, the email client, the email servers, the web server, the programming extensions of the web server, and probably much more. I'm using it all right now, and it's all Open Source. What's more, some open source programs have proven so reliable and useful that they have become a major part of the Internet's foundation, and key elements of the Macintosh and other operating systems.

But what about "Open Source Religion?" Here's a brief criticism of the notion.

Religion has no source code, in the same sense as software. That's not to say religion is not based upon something. The Christian Science cult, for example, is based upon the writings of Mary Baker Eddy. But are they not available for anyone to read? If that's the source code, then it's already open for reading!

The same is true of the Bible. We don't have the original manuscripts, but we have many ancient and reliable copies. Anyone interested can obtain the text of the Bible. It's already open for any to read. But it's not source code, to be altered, extended, or built into something bigger. The Bible is God's unchanging, proclamatory Word. That means it's not available for tinkering. If you don't agree, check out Galatians 1:8-9, or Revelation 22:18-19.

A prevalent thought through the ages is that religion is simply an accretion of mankind's beliefs and superstitions, as they might apply in any given context of place and time. In other words, religion is man-made. There are some calling themselves "Christians" who believe the same thing about the Bible. But how would the term "open source" even apply in that case? It comes from a different semantic context, and could therefore only apply by analogy or metaphor. Even then, it only applies to a small degree.

The source of religion can only be one of two things: human or divine. The term "Open Source Religion" assumes that it's human, and that people are trying to hide the basis for their religious beliefs. I don't see that happening, except in the case of certain cults where the leaders just make things up as they go along.

True religion must have its source in that which is divine. Otherwise, it's only a game, a guess, a hoax, or a means to influence others. That's why confessional Lutherans believe exactly what the Bible says; no more and no less. Some might argue that we have added the Lutheran Confessions to the Bible, but not anyone who has read the Lutheran Confessions. And yes, you can read the source, though if you want it in the original languages, you'll have to buy it.

The term "Open Source Religion" makes no sense. It's a clumsy label for the desire to invent one's own religion, and that's nothing new. So many people have always wanted to treat the religious landscape of the world as a smorgasbord, taking in only a bit here and a bit there. Nobody can really stop them, but it's stupid anyway, and will prove to be self-destructive. Again, it assumes that all religion is man-made, which a false assumption. The truth is so much greater than that, because God has only revealed what we need to know in His Word. Isn't it about time to wise up and understand that God must be greater than we are, not lesser? Isn't it about time to recognize our human limitations and seek wisdom while it may be found?

I'll continue using Open Source Software, and I'll keep opening the source of my faith too, the Bible. I'll open it for myself and for those for whom I'm called to teach it. It stands open of its own accord. I thank God that He has revealed His Word to us, and that Jesus of Nazareth truly lived, died, and lives again: true God and true Man, to redeem us from the blindness and guilt of our sin and unite us again with our Creator!

Paul E. Kretzmann was on the faculty of Concordia Seminary in St. Louis. He contributed the following book review for the Concordia Theological Monthly, which was published in the January, 1933 issue. He was reviewing Screen and Projector in Christian Education by Paul H. Janes. I include the review as a reflection upon how times have changed, yet good judgment does not.

The scope of this book is more exactly shown by its subtitle: How to use Motion Pictures and Projected Still Pictures in Worship, Study, and Recreation. The author rightly says: "With the addition of motion-pictures, projected still pictures, prints, photographs, models, maps, school journeys and reproduced sound, the educator has set out to stimulate a wealth of experiences to be used in the classroom to facilitate the understanding of the verbal symbols in books." (P. 14) We should like to emphasize the words "in the classroom" and add "in the church hall," because visual education has proved an invaluable aid in the work of our parish-school, Sunday-schools, young people's societies, and the various auxiliary organizations of the congregation. Every pastor who desires to have accurate information concerning the use of visual education helps will be glad to use the information contained in this book. We cannot endorse the larger part of Chapter V, on "The Use of Visual Aids in Worship," because the doctrinal and expository sermons of the Lutheran Church will rarely require, in most cases not even permit, the use of pictures. There are other dangers connected with the indiscriminate use of visual aids, especially if the emotional element is stressed. To such as will make use of the proper discrimination this book offers fine suggestions.

Full disclosure: two weeks ago (on July 8) I delivered a sermon explaining Lucas Cranach's altar piece in Weimar. The altar piece itself provides the Biblical basis for both painting and sermon. It was the first time I've tried such a thing, and I would consider it a success. You can find the sermon over at the congregations' web site.

How is this different from other uses of motion or still pictures you have observed in a worship setting?

I enjoy music, but several years ago I promised myself that I wouldn't buy any more albums. They were -- and are -- ridiculously expensive, and the rules for sharing, borrowing, and such were so restrictive that "buying" CDs no longer made any sense. Beside that, I have plenty of CDs already, but usually find myself out of range of a CD player.

(I don't spend lots of money on portable gadgets like music players. My only one now is a Palm Tungsten E2, which I use constantly and appreciate for its long battery life.)

Recently I've been listening to my music collection in digital form. I've ripped nearly all my CDs to Ogg Vorbis format, a flexible, high-quality, royalty- and patent-free encoding. Most recently I've been ripping to FLAC, a lossless encoding. One reason for my reluctance to buy a portable music player is the paucity of players supporting the Ogg Vorbis encoding and useful with a Linux desktop. There are some, however, and I think some day I'll take the plunge. Meanwhile, it's been nearly alarming to see the intrusion of the wma (Windows Media) format into the arena of digital recordings, and also the various drm (Digital Rights Management) -encumbered systems.

But now, there's an alternative that will have me buying new music recordings again: Magnatune! Get on over there and check it out. Apple enthusiasts will tell me "We already have this with iTunes!" Not so. Magnatune is an online recording label with a growing collection of quality artists from a broad spectrum of genres. According to a current Linux Journal article, fifty percent of the purchase price of Magnatune music goes directly to the artists. You can sample full albums before buying them. At this moment, I'm sampling a delightful album from American Baroque called Mozart, 4 Quartets for Strings and Wind. It's wonderful music to work by, and I'm only on the fourth track. I may actually buy this album, not only for the music but to support the great work that American Baroque are doing.

When I'm finished sampling this album, I'm going to check out at least one album from American Bach Soloists. They have a recording of Bach's Mass in B Minor. I already have an outstanding recording of that, but I'm curious to hear the differences of interpretation. I'm already tempted to buy their recording of Bach's Cantatas Volume V, and I'm excited to sample an album of Heinrich Schutz music: Musicalische Exequien.

Later, I'd like to hear the music of The Seldon Plan, just because the band's name caught my eye. (Since first writing this post, I've taken a listen. The Seldon Plan is pretty good, but I liked the bluesy guitar of John Williams even better. I'm tempted to buy one or more of his albums.)

So, how much will I pay for the albums I buy? According to the same Linux Journal article, there is a minimum cost of $5 per album, and there is also a maximum. Within those limits, I'll pay what the music is worth to me. What a system! I hope Magnatune's business thrives. Understood in a non-theological sense, their motto seems to be right on the mark: "We are not evil."

Oh, and apparently, Magnatune also provides recordings in the Ogg Vorbis and FLAC encodings, among others.

I finally was able to contact our ISP about our personal Internet connection. It turns out that the local telco is locally upgrading its capabilities so that the "other" pair of wires that comes into the house will be usable.

In case you've never bothered to look, there are two pairs of wires in Plain Old Telephone Service. Phones only use one pair, and DSL has used the same pair by making use of such high frequencies that they don't interfere with telephones. At least, they mostly don't interfere.

Our ISP is now going to use the other pair of wires, so the DSL signal will be carried separately from the telephone signal. I'm a bit intrigued to see how well it works. The ISP is making appointments for on-site installs, probably to make sure that all the wires involved really have four conductors. A lot of telephone wiring has only two conductors, since that's all that anyone's needed for phone service. Most of our phone patch cables have only one pair.

The Plucked Chicken is not professionally hosted, and relies upon our home DSL connection. It's never been really fast DSL, but it's been reasonably reliable. Most of the time. It seems now that our ISP is making some changes to their DSL setup in this area. I need to call them back to find out exactly what and schedule a time for them to stop by and update things. I'm guessing it's a new DSL modem.

Anyway, since we received that message, our current DSL modem has been losing its DSL link intermittently. It actually requires a modem reboot for it to reacquire the link. So, if you can't get to the Chicken at some point, don't worry too much. I hope that things will return to normal next week.

It's just possible that these changes will hamper my ability to host the Chicken. Many ISPs seem to push asynchronous bandwith with blocked ports, turning their customers from fully-fledged (no pun intended) Internet citizens into mere end-users or consumers of content, with no possibility of participating in the production of content (hosting web sites, etc.). I really hope that our ISP (Gorge Net) won't try to herd us farther in that direction. We already have asynchronous bandwidth, and that's not helping anything. If you find that the Chicken is down for an extended time, this too-common, misguided ISP philosophy may be the problem.

I've been suprised at the interest in the Dvorak article. So, just for the fun of it, I installed gtypist to run through a few exercises and see what my current typing speed is. I was expecting to see slower speeds than I was typing before the switch to the Dvorak layout.

It turns out that I'm typing faster than before. On the sentence exercises, my word-per-minute speeds were about evenly split between the high 90's and the 100's. That's about 10 words per minute faster than I used to type with QWERTY, though I do recall occasionally flirting with the 100-wpm mark on a good day. In the word variation exercises using the Dvorak keyboard this morning, I registered in high 70's, approaching 80 wpm. Of course, I'm also listening to Sunday's Issues Etc. at the same time, and it's a bit distracting from the concentration needed to do those exercises right.

But again, I don't count typing speed as a major benefit of switching to the Dvorak layout. For me, it's the ergonomics.

I use the Dvorak keyboard layout. It's an alternative arrangement of the keys on the keyboard for better ergonomics. Most, if not all, computers can accomodate this layout through software drivers. There is quite a following of advocacy for the Dvorak layout, as well as detractors and debunkers.

I don't claim that the QWERTY layout is bad. It was designed in the 1800's, and was only one of several layouts used in mechanical typewriters, optimized for the smooth operation of those machines. Later, it won the popularity contest and became the only game in town. I used to type up to 100 wpm in QWERTY, usually in the 80's when I bothered to check. It got me a job while at seminary, and helped with many other things. I learned to touch type QWERTY by forcing myself to do it right, beginning on an old 286 machine. Most of my practice was typing the papers of fellow students for money. (They had already been written. But once I got to choose the title myself. "Henry VIII: Can't Get No Satisfaction, or Satisfaction Guaranteed?" Seriously.)

I made the switch to Dvorak well after I made the switch to Linux. I haven't regretted either one, though there is a price for each. The price for Linux is not in dollars, but in willingness to learn. Learning fits my personality, so Linux and I have been inseparable. Dvorak also requires a willingness to learn. In this case, it's willingness to re-learn, essentially retraining one's reflexes so that when I think "toad" the proper fingers jump into action. Why did I switch? Not to type faster. Who really wants to type faster than 80 wpm, unless you're taking dictation in the form of a speech or transcribing something? No, I did it for the ergonomics. I found that my carpal tunnels and my finger joints were aching, and not typing was not an option. So I figured out how to configure my OS (and later Windoze and MacOS), and away I went. Initially, the learning was somewhat hampered by the fact that my cheap keyboard still showed the QWERTY graphics. The easiest reference I had was an on-screen diagram. If you try learning Dvorak, I'd recommend buying an IBM model M keyboard and rearranging your keycaps. It's the best keyboard ever made, anyway. The one I'm typing on now was made in 1984, and still works like new. That's right: 1984.

It probably took me about 2-3 months before I was fully comfortable with my Dvorak performance. The adjustment was completely self-paced, with very few exercises. I found a typing tutor program that included Dvorak, and used it for maybe 30-45 minutes per week, tops. It was exciting to see my speed and accuracy increase. Soon I couldn't sit down and touch type on a QWERTY keyboard any more. Exciting, but that brings me to my main point: the cost of switching. (I'd gladly pay it again.)

So now I can't touch type on QWERTY keyboards, so when I use a strange computer, I'm either back to hunt and peck, or I reconfigure the keyboard temporarily. The latter is usually possible, and works well. Then, I have to remember to reset the keyboard when I'm done. Otherwise, someone else becomes frustrated. When I bought a keyboard for my Sony Clie, it only came with QWERTY drivers. So I had to open the driver program in my hex editor and rearrange the key codes until it was right. That actually worked rather well! But it illustrates the problem: I now type Dvorak in a QWERTY world. It must be like being left-handed. There are no Dvorak keyboards for sale. It's just not an economic possibility. This isn't because Dvorak is inferior, but because QWERTY simply dominates everything. (The fastest typer in the world uses Dvorak!) It takes real training to touch type, and training is expensive. Consider that the Air Force values its pilots higher than their million-dollar airplanes. It's not just because the Air Force is old-fashioned, and believes in the intrinsic value of human life. No, Mabel, it's the training. No wonder companies won't buy Dvorak keyboards.

The cost of living in a QWERTY world is mostly a nuisance. The real problem arises when I have to use my computer's CMOS or another hardware program that lives below my operating system. At that point, I need a QWERTY reference keyboard, because my fingers just don't remember where those letters used to be! That's also why it would be wonderful to find an affordable, high-quality Dvorak keyboard supported in the hardware itself instead of the OS driver. I understand that Apple actually made something like that once. Would that it could happen again!

Why am I willing to pay this cost? Because for me the ergonomics actually are better. I had been having some carpal tunnel and joint pain, but with the Dvorak layout, the stresses are all different. In fact, they're better overall than with QWERTY.

Should you make the switch? Only if you're willing to pay the cost. It's not terrible, but it does take some perseverance. Is that still in the American vocabulary? Maybe. I won't say that you'll type any faster than before, though you might. However, I will say that you will find typing easier than before.

Yesterday morning our Internet connection became flaky, then stopped. I spent some time over lunch getting it working again. It was a bit frustrating, and the closest I can figure is that it had something to do with the old hardware I use for everything. This web server is running on an AMD K6, 333Mhz machine. Yeah. But it does OK, almost all the time. With all that this machine does, which is much more than serving a blog site, I hardly ever have to reboot it. Linux tends to be that way. When problems arise, they more often than not are caused by flaky hardware. I've been blessed to have few such problems with this machine.

How liberating it is to be using Linux. Sure, there are still problems and challenges; there always are problems, even with Apple products. But at least with Linux (as opposed, especially, to Windows), I didn't pay good money to buy my problems. And beside that, there are fewer problems and more possibilities.

Enough about that. It seemed that my DSL peer wasn't responding to my pppoe configuration requests. I think rather that my NIC was somehow munging the requests or not hearing the responses. In this case, I did a reboot to reinitialize the NIC (I maybe could have just reloaded its kernel driver module, but that can be tricky when performing these things via SSH to a headless machine), and all was well.

Except... I had tried eliminating the MTU setting on my ppp and pppoe daemons, to see if it would allow me to get pppoe config responses from the peer. I hadn't restored the original setting. So when the network came back online, there was some really odd behavior. Until I finally remembered the MTU change, it was quite frustrating. MTU stands, I think, for Maximum Transmission Unit, which is a kind of throttle on the size of data packets that come in through the DSL link. It's useful and even necessary when those data packets have to carry some extra information just to make part of the system work properly.

My home network is masqueraded through this machine. (It's a bit more complicated, but the rest is not pertinent.) That means this machine handles all Internet traffic for the computers at home. The weird thing was that most web sites wouldn't fully load. The browser would make the initial connection, and then sit there waiting for more data. However, Google's web sites worked! How's that for strange? Apparently, Google's web servers are all configured to use a smaller MTU than most of the Internet. Other kinds of traffic worked, too, such as SSH to various servers on the web. Masquerading was working (though I often wondered how well). But apparently those problem web sites were sending data packets too large for our masquerading setup to handle, so the return packets weren't making it through.

I was up too late trying to get things working, and finally shut everything down. I'm sorry if having the Chicken offline caused any problems. But maybe my little experience here will help someone, or maybe I'll remember it for next time!