I’ve been having difficulties trying to update a Fedora 8 installation with yum. When I execute “yum update” I received the following error:

Transaction Check Error:
file /usr/lib/libsensors.so.3 from install of lm_sensors-2.10.6-1.fc8.i386 conflicts with file from package libsensors3-2.10.5-52.fc6.i386

When I try to remove lm_sensors, a bunch of dependant packages want to be removed, too (but that is not what I want).

I noticed there was a nagios plugin that was being updated called nagios-plugins-sensors. Removing that allowed me to successfully perform a yum update!

So, I typed yum erase nagios-plugins-sensors and yum removed the following:

=============================================================================
Package Arch Version Repository Size
=============================================================================
Removing:
nagios-plugins-sensors i386 1.4.8-9.fc8 installed 1.1 k
Removing for dependencies:
nagios-plugins-all i386 1.4.8-9.fc8 installed 0.0

Success!

It’s quicker to ask a blog search engine like blogsearch.google.com or technorati.com to find out what is happening with my Internet service than to ask Comcast. After struggling with quirky behavior (like only comcast DNS being able to resolve DNS queries and opendns and others failing) a search on the last hour of blog comments regarding Comcast let me know that they are having major problems.

I’ve been beleaugured with strange resource errors in a VBA-based Excel application while running it under Presentation Server. I had missing bitmaps, incorrectly drawn WMF images, unloadable bmp files, and error messages such as “Not enough system resources to display completely.” These issues would appear intermittently and were difficult to determine the cause. Oddly enough I didn’t receive error messages from the ICA client and these issues did not appear while running under Terminal Services. The issues seemed related to running out of GDI resources. After a lot of strife (mostly with the computer) I found the issue: the amount of memory dedicated to video. I had 5625KB memory dedicated to it and it needed more. I also had checked “Degrade resolution first” and would prefer to to “Degrade color depth first” so the application does not get confused with a different size display. After increasing the amount of display memory to 8192KB and also setting the published application to 16-bit color, my problems disappeared.

I’ve had it for quite a while and love it: a new and improved of my original GPS design for my D200. This time it’s smaller, practical and easy; just mount it on the flash shoe, plug it in to the 10-pin connector and turn it on! Within no time at all GPS coordinates will be flowing into the camera.

This version eliminates the need for the expensive MC-35 and even the special 10-pin connector. I’ve opted for a quick GPS receiver and encased everything in a small black box with a flash shoe mount. Because it is powered through the camera’s power source, a switch on the side of the box turns off the GPS. Version 3 should include a battery, rechargeable through a USB connection.

Read on for directions on how to create your own GPS. (more…)

I use Plogger as my image gallery and enjoy it’s simplicity. I also use iView MediaPro to manage my images and have a simple script (contact me for details) that uploads selected images to my gallery on this blog. It’s been quite a while since I’ve tried to run the script and tonight, when I did, it failed.

The failing portion was galleryadd.pl and it was giving me:

Error: incorrect username/password

The resolution is simple: plog-remote.php makes a reference to a $config global that has not been defined. By including plog-load_config.php the gallery remote functionality works!

To fix, add:
require_once("plog-load_config.php");

after the require statements in plog-remote.php.