Unfortunately spamhole’s day is mostly behind us though I wish I would have been familiar with it earlier. The spamhole application developers took the approach of developing spamhole for other like minded individuals to assist in battling the SPAM issues on the Internet by creating fake open mail relays as possible and thus tricking spammers into sending their SPAM into blackholes or honeypots. It would have been extremely satisfying to watch SPAM enter a spamhole fake open relay I had created and be redirected to nothing. The spamhole application is not working as of Backtrack 5 R3 and is explained in more detail below.
Recently I had a hard drive crash that was in a Windows XP laptop. The drive would not mount under Windows however I was able to eventually mount it under Linux and rescue some of the data. In this article I will describe how to verify the USB hard drive enclosure is seen on a CentOS Linux computer and verify that Linux is able to see the USB device and the drive.
First you will want to remove the hard drive from your Windows XP computer and physically mount it into the USB hard drive enclosure. This will involve connecting it inside (IDE or SATA) and then plugging the USB cable or cables into the CentOS server. Since the hard drive is damaged its hard to know if its not reading it or if you have something misconfigured, a loose cable, etc. Below are a couple tips to make sure that the hard drive is being recognized via the USB connection.
I have had a problem with a personal WordPress blog I installed a long time ago but never got the chance to look into until recently which is the fact that the logon part of the site was not auto logging me on. Not only was the blog not auto logging me on but it was not remembering my password though it would remember my username. This blog has been around since before WordPress 2.5 and I have upgraded from time to time. I remember the issue started somewhere around the time that I upgraded from WordPress 2.5 to WordPress 2.6 so that is where I started the troubleshooting process and sure enough I was able to find the answer pretty easily. I had been in a rush when upgrading the site and once I had time to go back and read the documentation I found some configuration file options located in wp-config.php that had been added with WordPress 2.6. There were 3 security key configuration options added in WordPress 2.6 and fourth security key added in WordPress 2.7.