Holiday Cheer, Holiday Uncheer - Part 2
Continuing my holiday machine maintenance saga I move on to some notable trials and tribulations with Ubuntu, but not before I report on a little more holiday cheer.
I'm losing my wits. In my last article I forgot to mention that Jean-Pierre Lemoine has updated his AVSynthesis to version 25_05_09. This release includes new features for realtime control of audio and video parameters (Figure 1), opening a new way to explore this amazing program. I also failed to mention that discoDSP has updated the native Linux version of the Discovery synthesizer to release number 3.1 (Figure 2).
Un-Fun With Ubuntu 8.10
In a previous article I wrote that I'd report on my ongoing work with my new HP G60-125NR laptop and its brand new Ubuntu 8.10 distro. As I said in that article, there are many things to like about the Intrepid Ibex, but there are also some major annoyances that rival the experiences I had with Ivy's XP system.
The first annoyance was the Synaptics touchpad control. The machine includes a hardware switch to disable the touchpad, but it doesn't work. Fortunately I can turn off the touchpad with the GNOME Control Center's mouse control dialog. Unfortunately the process also switches my Fluxbox theme background to the Ubuntu default image. That image is nice, but I didn't ask for it and I don't like the system switching to it without my approval. I searched Google for an alternative and found the synclient utility. Alas, that software requires a configured SHMConfig, so I went back to Google to find out how to enable SHMConfig. My first attempts were made by adding appropriate lines to the meager /etc/X11/xorg.conf, to no avail. I then discovered that xorg.conf is no longer where the appropriate changes should go. X11 input devices are now defined and registered in the HAL .fdi configuration files located at /etc/hal/fdi/policy/. I created an shmconfig.fdi according to this design :
<?xml version="1.0" encoding="ISO-8859-1" ?>
<?xml version="1.0" encoding="ISO-8859-1"?> <deviceinfo version="0.2"> <device> <match key="input.x11_driver" string="synaptics"> <merge key="input.x11_options.SHMConfig" type="string">True </match> </device> </deviceinfo>
With that file in place I added this command to my custom start-up script :
I run the script after logging in, and I have no more trouble with the touchpad.
Update 28 December 2008: I reinstalled the system and decided to stay with GNOME, even though I do not like it. My touchpad settings in the GNOME Control Center are now persistent between sessions, though little else about the system has changed.
My start-up script also disables another HAL feature. I noticed that the hard-drive light flashed excessively during normal operation. Eventually X performance would slow to a crawl, so I checked with the good Doctor Google and learned that this problem and its solution are also well-known. The endless disk reading halted after I added these commands to my start-up script :
hal-disable-polling --device /dev/sdb hal-disable-polling --device /dev/scd0
Highly aggravating endless looping seems to be a design characteristic of Ubuntu 8.10. I recently learned that clicking on the Help button in a GNOME application will launch an infinite series of borked help pages, stoppable only by power cycling the machine.
Finally I come to the last and most annoying problems I've encountered with the Intrepid Ibex. Its shutdown, restart, and logout processes do not work properly, and I've yet to resolve them to my satisfaction (and yes, I keep this system updated).
Shutdown and restart just don't. The system hangs after the "Will now halt" or "Will now restart" messages, but I did find a workaround at that point to avoid pressing the machine's power switch. If I issue a ctrl-alt-del reboot command the system restarts cleanly. Then I can shut down the machine cleanly by booting into recovery mode, selecting the root prompt from the recovery menu, and issuing a shutdown -h now command.
The logout problem is more serious and I've found no solution for it yet. If I issue a logout command (e.g. Ctrl-D) in an terminal window the cursor simply skips to the next line and stays there, the xterm doesn't close, and the entire system is unstable and requires a manual power cycling. All because of a logout bug.
The real un-fun begins when you start Googling for answers and find dozens of them, none of which work for you. I assume the best intentions on the part of the Ubuntu developers, but these problems remain after the most recent updates. Meanwhile I'll continue to scour the many (too many?) Ubuntu user forums and wikis, hoping to find a fix that will work for my machine. I also welcome any and all polite suggestions that my readers may have, so please feel free to share your own insights and/or advice in the Comments section below.
At this point I rate the un-fun factor for Ubuntu 8.10 at a solid unrespectable 9. Its instabilities obviate its use as an audio production workstation, and only some of its notable virtues keep me on it. At one point I wiped Ubuntu from the drive and reinstalled OpenSUSE 11, only to discover that there are fates worse than Ubuntu 8.10. For the moment I've returned to the Intrepid Ibex, but I will say that I'm not at all happy about its egregious bugginess. I'm not the only user pleading for relief on the Ubuntu forums, but alas, there are only so many developers available, and the bugs remain. For more opinions, check out this poll of users' experiences after the install/upgrade to 8.10. The results of that poll are not encouraging, with by far the greater number of users reporting unresolved problems with Intrepid. On the more hopeful side, if the Ubuntu developers can resolve the shutdown, restart, and logout issues then the Intrepid Ibex would lose most of its un-fun factors. We await the day.
Despite its blemishes and shortfalls I'd still choose Ubuntu over XP any day. I'm not sure I could have repaired Ivy's system without it, and I must shout out great thanks to the Ubuntu team for such thoughtful amenities as Ubuntu Live and the creator for a bootable USB drive. One thing is certain: I could never have repaired a Linux system with Windows tools. Maybe it's possible, but it's obvious which system truly believes in openness and transparency, and I simply find it too difficult to work with a system so opaque as XP. Yes, I'll admit it, I've been spoiled by Linux. Alas, I'm not so thrilled with Ubuntu 8.10 as I'd like, but for various reasons I need to use it.
Happy Holidays !
I'll be back soon with a 2-part series on the Buzztard project, including an interview with team leader Stefan Kost. Until then, may your days be merry & bright, and I hope everyone has enjoyed an excellent holiday season.
Similis sum folio de quo ludunt venti.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
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