March 2009 – Steve Dougherty's Blog

Chrome and WP-Cache

I’m using Google Chrome now. I’ll probably set up Privoxy to get rid of ads, as I kinda miss Adblock Plus already. On a more philisophical note, I’m somewhat confused as to why more sites don’t offer subscriptions or donations instead of ads. When the house was quiet and I pulled up Chrome, I noticed it was almost constantly accessing my disk. Through Google I learned that the solution is to disable pishing and malware detection, which is somewhat concerning, but I don’t want the thing abusing my hard drive. I uninstalled WP-Super Cache and now I’m just using WP-Cache. With lighttpd I think I only used the WP-Cache part of WP-Super Cache anyway.

Also, I found a screenshot of 4chan on Reddit, where someone had posted this sentence:

Has anyone really been far even as decided to use even go want to do look more like?

The strange part is when I first read that I didn’t immediately realize that it was nonsensical. Chrome is also reminding me just how horrible my favicon is by putting it in a more noticable place. I should change it to something more bearable.

Cleanup

Just as Vertex mentioned, it is much, much easier to do a fresh Windows install and move over documents than it is to clean up an existing one. Apparently Dell puts (or put, this is an old machine, but I wouldn’t expect this to have changed) RAM that is slower than what the motherboard can take as a cost-saving measure. This things really flies now, and it POSTs so fast that I have trouble getting to BIOS or the boot device menu in time.

That being said, I am once again appalled by the out-of-the-box driver support in a fresh Windows install, even that provided by an SP3 CD. The device manager was no help for finding out the names of the sound, video, and ethernet drivers I needed, so I booted up into Damn Small Linux and did an lspci, which told me what I needed to know. Searching for drivers based on chipset versioning is not too fun, but it worked. The graphics were greatly improved from the 4-bit color, very low resolution they started out in, which was nice. The ethernet driver was a bit harder, because when I downloaded it, it wasn’t an installer, just a series of folders with three files. I went to the add hardware wizard, but it turned out I needed to let it fail, get past the check Windows Update pane, and then it would let me tell it where to look. The operating system seemed too proud of itself when it completed.

I had trouble finding an audio driver, and so did Windows even with a Windows update connection. I was very pleased to find that Dell had the audio drivers, which they made easy to find and download. Adobe annoyed me when I installed Acrobat Reader, as my client requested, because it decided to place another shortcut on the desktop that I didn’t ask for, and I feel it tricked me into installing Adobe AIR. The shortcut then wouldn’t go away – I couldn’t delete it – so I ended up booting into System Rescue CD to get rid of it because it annoyed me so much. I couldn’t delete it even running as administrator.

The whole thing ended up taking somewhere around 7 hours, but closer to 4 or so of those were actual work, lots of it was waiting for a virus scan. I wonder what I can do in the future while waiting for progress bars. I did start installing XP while I waited. I’ve also moved to a different method of charging for my labor. When I was working on friends’ gaming rigs, I just charged 10% of the hardware costs, which seemed reasonable. Dad suggested I charge hourly. I have a cap, though, as to not let labor prices get too high. I feel uncomfortable charging large amounts of money.

Logic Tables!

I was instructed to make code that toggled a Boolean if an input was currently true and had been false during the last loop. I did not realize that this was my task until I had taken a vague understanding from my given assignment and made a table of the possibilities, which Mike called a logic table when I showed it to him. I also learned that two false fed to and does not produce true. And only produces true if both inputs are true. In my defense, my thinking was getting fuzzier as I was getting confused, I was just trying various combinations to see if they worked, and I haven’t done logic loops like this before. I’m glad I know this now, it should prove to be useful.

Graphics Card Dead?

I think I just fried my graphics card by trying to put on a new heatsink. It only booted up once, and for a few seconds before the screen went blank. Now it won’t POST with the card in.

I was having problems with the fan making annoying noises. Over a period of a few months, XFX managed to send me a new heatsink. There were no instructions, so I looked up some guides on YouTube. I think the problem was that the coat of Arctic Silver wasn’t complete when I first booted up. I’ve had bad things happen every time I’ve used Arctic Silver. With it, I’ve gummed up a processor, killed a motherboard and CPU, and now fried a graphics card. Maybe I should get generic thermal paste and just leave Arctic Silver alone.

Migration

As I perform user migrations, it occurs to me just how nice it would be to have a seperate /home partition. This is possible, and it’s even an explicit option in the Debian installer. That would help not only with migrations from box to box but also changing servers on networks with a home directory on NFS.

My sister now has the old server as her desktop machine, and her old machine is now a BOINC zombie.

lighttpd!

This server is now running lighttpd. I’d capitalize it but its creators don’t. Most of my problems were caused by WordPress and its insistance on Apache’s .htaccess, (for fancy permalinks) as well as WP Super Cache. The workarounds that are out there ended up redirecting nonexistant things to the main page, something I found unacceptable. I don’t use the directory structure style permalinks, so I didn’t end up using any of the workarounds. WP Cache works fine, although my understanding is it loads PHP to serve cached files and thus is more intensive. WP Super Cache uses rewrites to avoid PHP and directly serve its files. It was really difficult to get this all working, but it is much more snappy. There was around 6MB free RAM on the Apache 2 machine even though it had 603 MB. The new server has 503 MB (an unfortunate thing I realized just now as I looked it up) and has 115 MB free. I hope it stays that way, and that there aren’t stability problems.

pfSense and lighttpd

I upgraded to version 1.2.2 of pfSense after I noticed syslogd was eating as much processor time as it could get. I hope that doesn’t happen again. Earlier when I tried BandwidthD, it didn’t seem to collect any data, even when I gave it the time it asked for, but I reinstalled it after the upgrade and it works fine now. It’s collecting data on the LAN interface, so I guess it’ll count in-network transfers too, or maybe within LAN stuff will just go straight through the switches? I don’t know, but I suppose it will be easy enough to find out with those handy graphs. The next step will be figuring out if I can have it monitor both the LAN and WAN sides. The upgrade process was really nice. There’s a page in the interface where you can upload the firmware upgrade from your local machine. If you enable SSH and log in, it can even pull down and verify the firmware on its own or upgrade from a file on the router itself.

The lighttpd test server is progressing nicely, after the people in #wordpress helped me with the redirect problems I was barely aware I had. A feature of WordPress is to redirect traffic that isn’t going to a defined blog URL to that URL. This meant that going to the test server on port 81 would redirect me to my main server, which got even more crazy when my pfSense DNS listings pointed me to the test machine, except on port 80 where there was no server listening. Someone in the #lighttpd channel helped separate PHP launching from lighttpd, which I’m not sure is something I want to stick with. If I do, I think I’ll have to add an init.d script for it.