Decreasing Returns: Put the Brakes on Rolling Release

In Economics, we speak of the principle of decreasing returns. At some point, putting more resources into something no longer produces as much profit. As the thing becomes more complex, it gets more difficult to move forward without making major mistakes.

A part of my assertion about the problems of rolling release is this concept applied to software. Is it possible someone can produce software which satisfies most needs, is almost totally bug free, and simply needs no improvement? I realize the question is hard to separate from the issue of user comfort. Yes, some people are still in love with WordPerfect 5 for DOS, and still pay money to get a copy. It’s impossible to say it’s superior to later versions, nor simply whether it is the principle of decreasing returns for that individual. It’s the subjective sense they can’t be more productive, and don’t want to invest more time in learning something newer. It seems nobody listens to them. We find marketing drones are entirely too concerned with some indefinable image consciousness, and seldom in step with actual consumers, so it can be profitable to keep an old product alive as long as somebody is buying it.

Take away the idiots who only think they know what’s going on, and you find most software packages pass through a cycle when they are a brilliant concept not yet fully implemented, through a series of very popular releases, into irrelevance because the most recent managers lost the vision. Could the product but have been managed, they would have known when the stop and simply support a good thing until it no longer sold. Yes, we have to contend with the tendency of corporate buyers to believe any marketing baloney that simply strikes some unreasoning chord, but there remains a certain core of buyers who feel cheated when you stop supporting something they truly value. This explains why the likes of Enable O/A still has a user base who struggle to keep it running on differing implementations of the necessary underlying DOS environment. That ancient office suite was nearly the pinnacle of what folks actually need to get business done. Simply adding a GUI would have kept it ahead of the market, but some corporate droid decided to sell it to MS, who buried it so they could promote a clearly inferior office suite.

We already have a vast supply for the people who can’t wait to buy the next new hardware gimmick, and the software to exploit it. What so few in the Open Source community realize is that sort of user is the minority. Sure, worldwide they number in the millions, but the world’s population is measured in billions. By now, the majority of that population has encountered a computer. There might be a period of fascination, but once they have assimilated the thing into their lives, it is for most of them relegated to the status of a tool, not a god. So keeping development going to make use of newer hardware technologies is almost a necessity, since most computer hardware tends to die all too soon, and the newer stuff is so very different. However, there is a growing number of computer users who just won’t notice much, and aren’t likely to care about even that little. Keep the hobby alive, because something truly essential will inevitably arise from all the feverish activity.

For the vast majority of computer users, though, we’ve already passed the point of decreasing returns. Feature saturation has set in, and it’s time to consider keeping alive a branch of some projects which have already produced something good enough for most of the world. When you have a winner, stick with it. Fix the bugs, make it work better. Tighten the code, remove unnecessary layers of abstraction. This goes for underlying libraries, as well. I can’t recall the article I read long ago, but someone was able to explain in terms I understood: The main cause of bloat was not always new features in the userland software, but in the libraries used to build it. Is there a release point where we have good enough libraries, too? Keep that product alive, independently if necessary.

If computers and the software don’t serve the needs of humans, the industry needs to die. If we can’t develop without proposing to define for them what they need, as if we were somehow a superior class who justly dictate what users will do, we have no moral ground to stand on.

Posted in computers | Tagged | Comments Off on Decreasing Returns: Put the Brakes on Rolling Release

HTML Word Processing

The basic purpose of a word processor is to format text for printing. If you aren’t going to put it on paper, you really have no need for a word processor. However, I find a huge portion of the computer using population don’t make a distinction between documents and webpages. That is, not consciously. They know instinctively if they want to print the contents of a webpage the way they want it to print, they’ll have to copy from the page, then paste into a word processor, format, then print. They focus on the presentation, and the information is a separate issue. Indeed, the former often takes precedence.

The problem here is such users seldom have much more than a semi-conscious awareness of their own preferences, even when they focus on presentation. They have no idea what makes presentation effective to their audience; they simply assume people are impacted as they were at that particular moment. Tomorrow the same printed page becomes trash because it doesn’t speak the same. No one seems to notice. People who have studied the issue of how the average brain processes information are more likely to reduce all the trashy, flashy extras in presentation, and stick with the essentials. They know all caps, all bold, all italics, all underlined, all brightly colored means the average brain says the message must be unimportant, because it requires such a hideous paint job to convey the importance the sender attaches to it. And we all know most people are more impressed with themselves than most other people are. Save the theatrics for the live presentations; in print there are precious few with a talent for it.

Unload all the silliness, and you arrive at the information itself. Adding attributes to plain text has a well-established meaning. The framework was established long ago, and various attempts were made to produce software which approximates that framework. Some details have shifted around a bit once standards were established for text displayed on a computer screen. What we used to do in print won’t exactly work on computers, and for most uses, print has shifted to match what we do on computers. For example, it’s no longer acceptable to indent the first line to mark the beginning of a paragraph. Now we use vertical space between paragraphs, and leave lines unindented in the main text. We still set off large blocks of quoted material by indenting the whole paragraph, so there is some overlap. Whole books have been written on the details. The point has always been: What’s the best way to inform the widest audience?

In the end, we have web publishing standards as reflected in the system called HTML — HyperText Markup Language. That framework continues to develop, but it’s now the reflexive standard in the minds of most people who can read. Over the years, I have found myself moving away from the word processing model altogether. While I still have a printer attached to my computer, I seldom use word processing software. For things which must be printed, I prefer a typesetter (Lyx), but for most things I prefer either plain text or HTML. All the more so since, even for printing, HTML processed by your browser seems a better way to go.

That is, it’s possible to write formatting instructions (CSS — Cascading Style Sheets) for inclusion in the webpage display which can be tailored just for printing. Even then, the whole idea is to avoid making choices for the reader, and giving them maximum freedom to alter the presentation quite a bit. Of course, that means they’ll need some awareness of what they can change and how, but for those who don’t know, the basic standards are probably fine. I use minimum formatting, with one CSS for browser display, and another for printing. This lends itself to a certain global accessibility, since neither directs the result to fit a particular size of paper. My printer CSS allows the user to print on any paper, because it’s solely an issue of browser and printer controls. All I do is provide relative guidelines, and those who really must change those can do so by telling their browser to prefer their own CSS over mine. I construct my CSS files specifically to be advisory, and easily overridden by anyone who has the savvy to set their own user-CSS.

On the one hand, this forces me to focus on the content. It’s pretty much the same for typesetting software. In my best academic style, I try to limit the use of italics, boldface, and reserve underline for marking hyperlinks. If you really need white-on-black, you can tell your browser to make it so, and it should work fine. If you really like blinking text, you are free to learn how to make it happen and apply it to my webpages. You can print any color you wish, because I only suggest black-on-white as the most common style. Depending on how your browser and printer cooperate, printing my webpages should work about the same as with a word processor.

I used to have a huge cache of word processor documents, and always worried about the format and whether anyone else could open them and print them. Over the past few years, I have changed them all to HTML. It’s become the most widely acceptable format for just about any purpose.

Posted in computers | Tagged | 1 Comment

Opera Reconsidered

CentOS isn’t all that friendly to standard desktop use, but it can be tamed. It has become my choice because once I get things working, I can pretty much expect it will continue working for the next couple of years, at least, with full security and bug-fixing support. Meanwhile, anything I build or add from outside the repositories will continue to work for just as long.

While I don’t really like Flash media junk, entirely too much of my interaction with people important to me requires I be able to run a Flash player. The Open Source projects — swf and gnash — just aren’t there, yet. I’m doing my best to keep everything 64-bit, especially multimedia stuff — better sound and better video quality. Not too long ago, Adobe released native 64-bit Flashplayer for Linux, so my excuses were gone. The tar.gz just opens to a single plugin file, and you have to make the appropriate symlinks yourself. I can handle that.

Firefox won’t use it. The about:plugins page shows it, and so does the Plugin Manager, but all I get is a blank spot in the webpage. So I decided to try Opera, which also recently released a full 64-bit version. Oddly, I’m not getting the spastic unexpected mouse gestures I complained about previously. What I am getting is a very smooth integration of Flashplayer in Opera. So for now, Opera has redeemed itself on my system.

Posted in computers | Tagged , | Comments Off on Opera Reconsidered

CentOS Fix: GNOME Mahjongg Scores on “Difficult” Level

This is pretty minor and doesn’t warrant much discussion. When you play Mahjongg on the default game called “Difficult,” upon completion of that game a window pops up saying your score qualifies for the Top Ten. However, the window is empty, no scores are shown, and you can’t do anything with it except close it.

The fix was found by chasing bug reports for the upstream GNOME Games channel. As root, edit the file /usr/share/gnome-games/mahjongg/maps/mahjongg.map at line 311:

<map name="Difficult" scorename="diff">

should be

<map name="Difficult" scorename="difficult">

The game score file name in that control file doesn’t match what is created by the package in /var/lib/games/. That it was not fixed until the next release just shows the standard GNOME developer attitude of moving onto the next release without fixing the previous one.

Posted in Uncategorized | Tagged , | 2 Comments

More on Rolling Release

Let’s get one thing clear: I utterly despise the brand of morality and ethics displayed by Microsoft. Gates knew a thing or two about computers, just enough to steal everything he built; he never comprehended the difference between good and evil. To this day, his utterly broken moral compass still affects the way Microsoft does business. However, to a large degree, he simply continued what was already in place in the business world. He remains a primary example of what’s wrong with that world. For example, when you buy a system running Windows, you are not the customer. You are the product delivered to MS business partners, generally in the form of a system so shot through with intentional security vulnerabilities, you are forced to surrender your privacy and your eyes to a tsunami of advertising. The only “malware” MS attempts to squash is from companies who won’t play nice with MS.

There is, however, a few things MS does right. Have you ever noticed you can run multiple versions of a particular library on Windows, and each application knows which one it should use? Try that on Linux. Here we sit some eight years later, and just about every software product I can buy for Windows will run on Win2K. And notice Win2K is still supported by MS. Buy a Windows server once, and for at least five or six years, the only complete upgrade required is for a few third party packages. If any particular package needs later versions of some library, just add them. You cannot do that in Linux. On a private mailing list, Jonathan Brickman said:

This is all the basic rub, with Linux packaging+library standards. And non-package app delivery standards run into Linux P+L as a brick wall. Just for one instance: I have an old eight-core server with two gigs of RAM, built for RH Enterprise 3 and still running it nicely. I would have loved to add a number of things into it, convert it into an application server, but the glib is so old that many things just won’t go without a complete recompile, which would mean getting a whole lot more dev libraries, et cetera.

Well, you could in theory, I suppose, but nobody does it that way. Not often, at least. I can recall a single incidence where I was running SuSE 8.2, and someone was building GNOME packages. One particular application required a later library, so the packager installed it in its own directory, labeled in part by the release number, then had his package refer to that library directly. But that’s not the Open Source way. In fact, such a concept seems to be held in contempt among Open Source developers.

That is, except for a few projects. For example, I can go to the Mozilla folks and get a copy of Seamonkey, still working fine on older machines, and even a version with the old Gtk1 interface. That would probably run quite well still on clones of RHEL 3, and certainly on 4. Yes, there are machines out there still run some of those old clones (CentOS and Scientific Linux, to name two) and those are still supported from the upstream RHEL distribution until 2010. And did you know? RHEL 2 is still supported until sometime in 2009. That’s roughly the same as the old RedHat 7.2 — released in October 2001 — almost as old as Win2K.

I didn’t post this to sing the praises of RedHat and friends. As I understand it, they did some of their customers dirty when they sold support licenses for 9.0, then simply dropped it. However, that hardly compares with the consistent and persistent mean-spirited behavior of MS. RedHat does compete well in terms of business expectations. The next nearest support level comes from a handful of Linux distros supporting their releases as much as three years, among them openSUSE, and certain Ubuntu releases (labeled “LTS”). These are the versions you can get for free. Both RedHat and Novell support their commercial versions now about seven years each. Buy a server, install the OS, both last about the same and things are simpler. That’s the sort of life-cycle business like. With this sort of support, we can expect to see Linux making some inroads in the future.

Except for one problem: third party developer support. That is, those who are developing stuff to run on these systems tend to ignore the commercially stable distributions of Linux. It’s one thing for me to upgrade ALSA in place on my CentOS 5 box. That’s pretty low-keyed, and the instructions are easy to find. It affects only one element of how things work. However, if I want a better webcam application, such as Cheese, I’m out of luck. It won’t compile on my CentOS 5 box unless I upgrade the entire GNOME system installed. I find it odd the folks writing GnomeSword can make it so I can compile their latest and greatest, but not Cheese. I don’t know the difference at the code-writing level, but I wonder what this is which makes some developers spare no concern for supporting anything but the latest and greatest distros of Linux.

The people running these projects seem to have no comprehension how this cuts them off from wider adoption. I can get OpenOffice, Seamonkey, and even commercial products like Opera to run on much older systems, but far too many popular desktop software applications exclude those of us for whom Linux is not merely a hobby. Also, I realize projects tied tightly into the major desktops (KDE and GNOME) are worse about this than those projects which use other toolkits, or which aren’t so tightly woven into the desktop itself. For example, you can use both Qt and GTK libraries in such a way as to make applications compile on a very wide range of release versions. Projects linked to Motif/Lesstif, FLTK, Tcl/Tk, and other, or multiple, interface toolkits probably represent the best of breed when it comes to opening the door to inclusion. Perhaps the problem is more a matter of the culture within those large desktop projects. All the more is this a serious problem, since these are vying for wider adoption as “the Linux standard” in industry. If so, they guarantee it will never happen.

Posted in computers | Tagged , | 3 Comments

Return to Sanity: CentOS Is Home

After a few days of testing Debian Lenny AMD64, I just can’t make it home. Yes, the packages are newer, and once it hits “stable” in the Debian developer cycle, it will be supported for a long time. Still, there are a couple dozen little things which just don’t feel right, and I can’t get used to them.

CentOS is home.

Posted in Uncategorized | Tagged , | Comments Off on Return to Sanity: CentOS Is Home

Dream Ride: Mass Transit

Thanks to the US military service, I spent quite some years in Europe. I must confess I prefer living there over living in the US, but I could never afford to go back there on my own. I’m not too sure any of those countries would want me, since I’m not highly productive in the economic sense. Still, I got comfortable with the atmosphere and other languages, and could spend my declining years there.

It’s not a simple matter of externals. For example, I admit I really enjoyed their mass transit systems, something we will probably never duplicate. I’ve read a lot of analysis why this is so. Most of it points out our far lesser population density, and how we do have mass transit systems in big cities. There is also the argument the Europeans are fundamentally more comfortable with high taxes and socialism. These points are valid, but miss the much more fundamental difference: We are more emotionally involved.

It’s not as if there is no passion in Europe, but it runs in different channels than for us. Most of the residents there would love to have a personal vehicle, a big house in the sprawling suburbs, and so on. However, they don’t consider it a basic right. For all our lip service to “reality,” our gut instinct here says having your own wheels is an utter necessity. We can hardly imagine planning our lives around a bus or train schedule, and you should hear the whining when I suggest walking more than a quarter-mile to get anywhere. Even with my arthritis, I can enjoy walking a mile or two along interesting routes, and that happened quite often when traveling in Europe, both on private and government business. Our problem is we take ourselves too seriously, and make it a matter of universal human justice if we are inconvenienced.

We are spoiled brats. When I traveled through various European countries, I seldom did things to stand out as a foreigner. More than just learning the language, I tried to maintain a live-and-let-live attitude. This is the fundamental nature of being “cosmopolitan.” I don’t have a vested interest in making you think and act like me. At the same time, I carry a sense of civil responsibility, of trying not to cause trouble for frivolous and merely personal reasons. I’ll be glad to make a scene for the right reasons, but that moment seldom arrives. Our brattiness shows in our corruption. It’s not as if I’m suggesting there’s no corruption in European government or other institutions, but it’s different. We self-righteously assume it shouldn’t be, but when it’s there, it’s just too pervasive and extravagant. Most often, it’s factored into business in Europe. That is, it’s not quite corruption in the greedy sense, but it’s taking liberties and being generous with everyone, not just yourself. I can’t count how many times in Europe little rules were broken in my favor by someone who could have been a grinch.

For all the secularity of Europe, they handle sin a lot better than most American Christians. Vices exist all over the world, but most Europeans are simply honest and matter-of-fact about it — regulate and tax it. We are prissy and silly — prohibit, then cripple the enforcement, using penalties as an excuse to oppress those currently on the political outside. Because of this, our American Christian witness is very weak, because we want to rule the world, instead of rule ourselves. This is what destroys it for us here. Rant all you want about the evils of socialism, but it’s only going to progress. The least we could do is figure out how to make it work, and make the most of it. Instead, it will be our destruction, because we as a nation are not mature enough to handle changes we can’t stop.

Posted in globalism, social sciences | Tagged , | Comments Off on Dream Ride: Mass Transit

Debian Lenny: 64-bit Pain

Debian has a different approach to 64-bit hardware. The entire system is 64-bit, and the only way you can run anything 32-bit is in a “jail” — a sort of security sandbox isolated from the system itself. I suppose this adds some measure of security, but it also offers a unique experience in pure 64-bit computing.

The Debian community once planned to make their distro a little easier to install and configure, adding the graphical installer as a first step. However, their upcoming Lenny (5.0) release candidate uses a very recent X.org package, for which virtually no Debian scripts exist. Sure, you can run the Xorg script to capture most of the hardware (Xorg -configure) and it will do just the minimum. I had to add an awful lot of information about my monitor to get anything useful out of it. When I added the nVidia driver, I had to wrestle with it for quite sometime, since it likes to ignore standard settings options willy-nilly and force you to accept defaults. Eventually I got what I wanted, but it was downright painful, because there is no single repository of information on this.

The other big headache was sound. While detection of the chipset was fine, there was a conflict with my USB webcam, which sports a microphone. The scripts and alsa-utils offer no obvious means to tell the system to load the webcam after the sound system. Finally, I discovered a very obscure tweak: adding a single last line to /etc/modprobe.d/alsa-base — options snd-usb-audio index=-2. So now my sound works beautifully and so does the webcam. Since I used the KDE installer for all this, I got Noatun for all my video and sound files. Oddly, the codecs provided by default actually played everything I had to test it. However, Noatun kept crashing, so I switched to Xine for some of the file types. However, as with CentOS, I find running video and sound in 64-bit makes a difference in the quality of the output.

Yet again the issue with Nedit was already worked out by the builders. Cheese was already built and available, so making optimal use of my webcam is already covered. I never did get an answer from the Cheese project on how to build it on CentOS. The primary flaw of Debian is no simple firewall setup. You can install any number of packages, but every one of them is far too advanced for the average home user, demanding decisions no ordinary user should have to make. On top of that, most of the firewall packages require reading a small book just to use their “simplified” management. This is carried over into Ubuntu and a few other Debian clones.

At any rate, once you struggle through the issues on Debian Lenny for AMD64, you won’t have to mess with it again for a very long time. The long release cycle for Debian offers plenty of time to get used to things, and good support for packages in each release. The only other hassle was not really Debian’s problem: CentOS by default uses volume management on harddrives, and hides carefully any options for avoiding it during the installation. It took some reading and poking about before I found out how to mount my CentOS drive to copy files over.

Update: I’m closing this post to any further comments. Some of the comments have been removed, so it may not make sense. I’m being spammed by a particular Debian freak who don’t understand: My choice not to use Debian should not be taken as a personal insult. The folks who run the Debian Project have no interest in meeting my needs, and that’s fine. This is not about superiority, but suitability.

Posted in computers | Tagged , , | 7 Comments

Gnomesword from Source

If I can’t get Bible search software for my computer, it’s not a good computer. Neither CentOS, nor any of the other compatible RedHat clones, offer a Gnomesword package for 64-bit. There is one source RPM set, but they were a bit older, and I felt I should be able to produce the latest version of both Sword (1.5.11) and Gnomesword (2.4.1). It was an adventure.

First, we build the Sword library. To have that search capability, we have to build Clucene. Again, not offered in the RedHat clones, so it’s easy enough to build from source. For this whole project, I allowed everything to install to /usr/local because that’s why that directory structure exists — stuff you want to use locally which isn’t part of the core system. It’s pretty much the same routine building packages from source. You unzip and untar in /usr/local/src and build according to instructions in the INSTALL file at the top of the package directories: configure, make, make install. Sword is pretty much the same. I already had Curl so I could build in the feature allowing downloading of modules directly from Gnomesword. Again, it was pretty much the same routine build process.

However, anything related to GNOME these days requires the pkgconfig stuff, and building Sword from source does not create the proper marker for pkgconfig. I had been through this once before long ago, but didn’t save the details in my personal help files. However, I knew I had posted it somewhere, and found it in the Usenet archives. I tweaked it to match current reality, but here’s the sword.pc file necessary for building Gnomesword:

prefix=/usr/local
exec_prefix=/usr/local
libdir=/usr/local/lib 
includedir=/usr/local/include


Name: Sword 
Description: Biblical Text Engine 
Version: 1.5.11
Libs: -L${libdir} -lsword 
Cflags: -I${includedir}/sword

With that in the proper place, I managed to build things just fine. Except: Sword does produce it’s own sword.pc, but I never knew it. I found it in the /usr/local files. It contained all the proper lib links, flags and everything. I went back and rebuilt with the one I found produced in the build process, quite by accident.

sigh

We live and learn. By the way, quite by accident I enabled the Mozilla-based rendering instead of GtkHTML, and find the Mozilla version vastly superior for my use. Having the Strong’s numbers under the line of text is more like the way the printed version appears. Fonts are more nicely done, too.

Posted in computers | Tagged , | Comments Off on Gnomesword from Source

CentOS Desktop: It Can Be Done

CentOS is a free Linux distro built up from the source packages used for making the commercial RedHat Enterprise Linux distro. RedHat doesn’t actually sell the Linux software, but sells the support services to keep it all running for businesses and governments. Like every other Linux distro, RedHat takes the raw code which goes into an operating system, packages it to suit their philosophy, in this case to meet their business plan. Because of the GPL copyright system, and a long history of engaging the Open Source community, RedHat makes available the pre-packaged sources for free. This allows other Linux projects to use those sources to build a distro very much like RedHat’s, but without the copyrighted logos and other branding. However good and stable is the RedHat Enterprise version of Linux, CentOS is the same thing without the expensive support tied to it. Further, the RedHat bug fixes and the 5-year code support is also copied.

Obviously, the whole system tilts in favor of enterprise use, not home desktop use. That doesn’t mean you can’t make it work the way you like. However, the emphasis on stability means you’re not going to have cutting-edge features. You can get some of them, but it’s more work. Those of us with some experience, willingness to do the work, and knowing whom and how to ask for advice, can tame this industrial grade operating system for home use. What follows is an example of things you might have to do.

First was the on-board sound chips on my nVidia MCP61 motherboard. While the kernel supports this, the bundled version of Alsa did a poor job of detecting and configuring it. I got a good sound test during installation, but it never got setup properly. In this case, the solution was picking up the alsa-lib-1.0.16 source RPM set (alsa-libs, alsa-utils) from Fedora 9. Since Fedora is the user community test bed for RedHat’s commercial releases, most of the source RPMs are packaged in a way they can be built on just about any RedHat derived distro. Keeping in mind FC6 is roughly the same as CentOS 5.x, we can still find plenty of SRPMs from later releases which still work. In this case, no tweaks were necessary. I already had most of the development tools for CentOS. Once the SRPMs were installed, it was a simple matter of rpmbuild -bb alsa-lib.spec. It required using --force to install that over the earlier version, but it was necessary to build the alsa-utils package. Once installed, it took only a reboot for me to have sound.

Second, I wanted my Logitech Quickcam Messenger to work. Research showed me my particular model was supported by the SPCA driver project. In this case, most of the work had already been done. It was necessary to add a third-party repository, but the packages were already built. CentOS has a good tutorial on their wiki. They also cover the preferred methods for adding kernel modules, in this case the Dynamic Kernel Module Support (DKMS). It was a simple matter to install the gspca support using yum, the favored commandline package management: yum install dkms dkms-gspca. A quick modprobe gspca and the webcam was working fine.

Most Linux users by now are familiar with chasing down the nVidia driver to enable full graphical acceleration. The CentOS project assumes you are competent to find the drivers and compile them yourself, but still offers a wiki page with effective instructions on getting it done. Not too long ago, nVidia began offering a driver for the 64-bit systems in Linux, and it works fine. You may also have heard of the freetype bytecode rendering issue. The recipe isn’t that hard to find, but in this case it required knowing freetype was recently updated, so I had to draw my SRPM from the updated repository. Then, I had to edit the freetype.spec to make sure it labeled the resulting RPMs with later numbers so the automatic updater didn’t try to replace it with the standard packages without the bytecode hinting, for which we went through all this hassle in the first place.

Other issues are simply a matter of what I like to use. Installing Cream on top of gvim makes it actually useful, and Elinks, using the latest unstable release (0.12pre2) finally provides a display free of ghost text artifacts. Nedit is my favorite for handling large text files in need of significant reformatting. The problem with Nedit is finding a package for 64-bit, then getting past the display issues. I found a decent RPM from the FC6 archives, but it crashed on my 32-bit color display. The authoritative answer is to ensure Nedit is called with a modified command to make it ignore a conflict between the X server and the Motif libraries. While some have recommended turning off the composite extension in the xorg.conf file, this affects too many other applications. The better options are to use either of these two modifications:

nedit -xrm '*visualID: default'
or
XLIB_SKIP_ARGB_VISUALS=1 nedit

This seems to solve the problem. I edited the GNOME menu to reflect the former arguments when starting Nedit, making sure to put the whole thing inside double quotation marks.

It’s been mine, and the experience of several others, that sound and video play on 64-bit, with 64-bit drivers and applications, can be much better than running the same hardware under 32-bit. I notice the sound is cleaner and fuller. Since RPMForge offers Mplayer and ffmpeg for CentOS, it’s a cinch to install them. The Mplayer project has lately been producing modified codecs for 64-bit which seem to work quite well on my system. The only other item I’ve felt a need for was a MIDI player. Since the Linux sound fonts aren’t provided by the hardware manufacture, there are work-arounds. I decided to build TiMidity++ from source, then install the eawpats sound files to support it.

There may be other issues and work-arounds necessary, related to the somewhat older packages on CentOS. Still, I am finding it so far worth the hassle. If you find these directions too hard to follow, or simply need a degree of hand-holding, feel free to ask for clarification.

Posted in computers | Tagged , | Comments Off on CentOS Desktop: It Can Be Done