Ext2Fsd BAD_POOL_HEADER BSOD on Windows 7
I have been using Ext2Fsd for a long time, everything was fine while using Vista. I decided to upgrade to Windows 7 after the release candidate was made available. For the most part everything was fine, until I started browsing my ext3 /home partition where I keep all my data. Sometimes I would get lucky and be able to open the file I wanted, however in most cases I was met with a BSOD saying something about a BAD_POOL_HEADER.
I am not a programmer, in fact I am probably one of the worst candidates for a programmer, I don't like it either. Thankfully for me though a gentleman named Bo Brantén developed a version that eliminates this issue. He describes the issue on the Ext2Fsd project page as a response to the posting of version 0.48. Apparently the issue was caused when the driver referenced memory after it was freed.
The updated version can be downloaded from the link below. Replace your ext2fsd.sys in C:\Windows\System32\drivers with the updated version and reboot.
Linux Based Cereal
Linux has entered the breakfast food market even with struggling with the desktop market. There is really no price difference with the Frosted Flakes coming in at $2.63 for 17oz and Sugar Frosted Flakes costing $1.78 for 12oz. While there is no justifiable ROI in buying the Sugar Frosted Flakes at least you get the satisfaction of a penguin on the box, am I right?
Installing VMware ESXi 4.0 On A USB Drive From Linux
Find what your USB drive location is (/dev/sdb for example)
sudo fdisk -l
Mount the ISO
sudo mount -o loop VMware-VMvisor-Installer-4.0.0-164009.x86_64.iso /mnt
Extract the image
tar zxf /mnt/image.tgz -C /tmp
Unmount the ISO
sudo umount /mnt
Change directories to the location with the image
cd /tmp/usr/lib/vmware/installer
Write the image to your USB drive
bzcat VMware-VMvisor-big-164009-x86_64.dd.bz2 |sudo dd of=/dev/sdb
How To Upgrade WordPress on CentOS 5 From A Shell
Below are the commands that I used to upgrade WordPress to version 2.8 on a CentOS 5.2 installation, hopefully you will find this helpful. Always be sure to backup your database and any customizations before you upgrade. I would suggest using WordPress Database Backup it makes things easy.
cd /tmp
wget http://wordpress.org/latest.tar.gz
tar -zxvf latest.tar.gz
rm -rf /var/www/wordpress/wp-includes
rm -rf /var/www/wordpress/wp-admin
cd /var/www/wordpress
/bin/cp -rf /tmp/wordpress/* .
Once you have done this go to http://yourdomain.com/wp-admin/upgrade.php and click the upgrade database button and you should be good to go. Once you have completed the upgrade it would be a good idea to backup your database again.
Configuring Apache and Zimbra on a Single Server
After configuring Apache on my new server I started in on Zimbra. After installing Zimbra I was unable to get to the administration console. Additionally I was getting the "zmmailboxdctl is not running" when running zmcontrol status.
I wanted to run Zimbra over HTTPS and wanted my Apache to use port 80 so I switched Zimbta to HTTPS (port 443) by using the following commands.
su - zimbra
zmtlsctl https
Zimbra documentation said to restart tomcat after running the commands but this did not work so I simply rebooted. I was still unable to get zmmailboxdctl running because Apache was still using port 443 for SSL. To eliminate this issue I changed SSL to another port by editing /etc/httpd/conf.d/ssl.conf. The lines below need to have the port changed to something other than 443. The third line below in my configuration was commented it out so I left it alone.
Listen 443
VirtualHost _default_:443
#ServerName www.example.com:443
Once this was done, Apache was restarted, I was able to start zmmailboxdctl successfully, and was then able to access the adminsitration conlole via https://serverip:7071 and Apache was still running over port 80.