Jeff Duntemann's Contrapositive Diary Rotating Header Image

Tutorials

How things work and how to do them

Fruit Wine and Pork Stew

Not much time tonight, but it's worth reporting a recipe that Carol threw together off the top of her head earlier today:

Pork Stew

Cut a two-pound pork roast (not a loin) into 1/2″ cubes. Sprinkle flour on a cookie sheet and then salt the flour. Coat the pork cubes with flour and salt, then brown them in oil. Add half a 750 ml bottle of some sweetish wine. We used Mountain Spirit Winery's Angel Blush, a fruit wine consisting of 40% apple, 40% pear, and 20% raspberry. Cover and simmer the browned meat in the wine while you cut up three Yukon Gold potatoes and two apples (we used Braeburns) into similar sized cubes. Simmer for three-four hours. It's not critical. Add water if the liquid level gets too low. The apples will break down and contribute some body to the gravy. Makes a lot; we should get three suppers out of it.

I tend to like sweeter wines, but I've never really warmed to fruit wine of any kind. I just finished the bottle of Breezy Hills Raspberry we brought home from Iowa (near Minden) last October, and it wasn't terrible but wasn't great. Fruit wines tend to taste yeasty to me, a little like beer, and I don't know if it's just a taste quirk of mine, or if I simply haven't tried any really good fruit wines.

The stew recipe was an experiment to see if stews (which can sometimes have a sweet edge to good effect) could be simmered in a sweet wine. The Angel Blush is a little too sweet to drink in any quantity, so we used it in the stew, and it worked very well. I don't think I would cook a darker meat in sweet wine, but for whatever reason, it went beautifully with lean pork. Give it a shot.

Booting Kubuntu from a Removable Drive

Pete and I discovered something interesting recently, almost by accident. Ok, it was almost entirely by accident. But it's useful nonetheless: We figured out how to install and boot Kubuntu on a removable hard drive after Kubuntu's installer failed to see the removable drive.

I've written about Dell's SX260/270 small form factor desktop here a number of times. It's a tiny little micro-tower made from laptop parts, especially Dell's Inspiron line. Its single most useful feature is its “media bay,” a front-panel slot that accepts several different kind of removable drives, including floppies, Zip 100s and 250s, CD and DVD drives of all stripes, and hard drives in appropriate cartridges. These cartridges are available empty, and Pete and I each bought such a cartridge plus an 80 GB notebook drive to install in it. The idea was to install Kubuntu on the cartridge drive, and then figure out how to dual-boot between Windows on the main hard drive and Kubuntu in the cartridge drive.

Except that I couldn't get Kubuntu's installer to see the cartridge drive, and thus couldn't do the install. Oh, well. We were interested enough in configuring Kubuntu and experimenting with some OSS titles accessible by KDE package manager Adept to pull the main Windows hard drive out of my SX270 lab machine and drop the new, empty hard drive into the main internal drive slot in its place. From there it was a typical and easy Kubuntu install, and we spent an afternoon trying things out. (Adept is a marvelous thing!) The next day I wanted to use my scanner downstairs, but the scanner software was installed under Windows, and HP infamously does not provide Linux drivers for its products. So I pulled the Kubuntu drive out of the SX270 and put the Windows drive back in. On a whim I installed the Kubuntu drive in my empty media bay cartridge and plugged the cartridge in to the machine's media bay to see what the boot process would do. I restarted the SX270, and wham! Kubuntu booted.

It's obvious in hindsight: The BIOS lists the CD drive ahead of the internal hard drive in boot order, and the CD drive lives in the media bay. In fact, anything with a master boot record plugged into the media bay will boot (or try to boot) before the internal hard drive.

There is a downside to using Kubuntu from the SX260/270 media bay: There's only one media bay, so with the Kubuntu hard drive cartridge plugged in, there's nowhere to put my media bay optical drives. (I could buy a USB optical drive, but that's yet another piece of hardware to keep track of.) The real solution is to figure out how to make grub dual-boot Windows and Kubuntu from separate partitions on the 120 GB internal hard drive. Remarkably, O'Reilly does not have a book on grub, even though they have whole books on numerous deep-geek software packages with user bases (barely) in double digits. (There are millions of grub installs. Maybe tens of millions.) So I've been reading the scraps posted here and there online and will figure it out eventually.

I guess I should have known that anything in the media bay would boot before the main hard drive. I freely admit that I didn't. Sometimes, well, you just get lucky.

The Power of Dust

In the past week or so, I've gotten unpredictable overheating warnings from my Intel motherboard monitoring utility. The CPU zone was getting up to 165 degrees while I was typing continuously into Dreamweaver. That Dreamweaver should be the culprit was not a total surprise; when I type continuously into the Dreamweaver editor, Task Manager shows CPU usage pegged at 50% until I stop. I don't know how they handle their data internally, but I intuit that every time I press a key while the editor has the focus, Dreamweaver does some kind of tree traversal of the entire document. (This comes from watching Task Manager's graphs while editing a short and fairly simple HTML document and then a large a complex one.) The mystery was why my CPU zone temperatures were gradually increasing from about 130 under load to 165.

Crack the case (which I admit I haven't done in almost a year) and there's no mystery: My CPU heatsink was caked with dust, and across much of the heatsink the dust had completely closed over the voids between the heatsink fins. My digital camera's lens jammed just after Christmas or I would have taken a picture, but it was impressive, and what was even more impressive was the cloud that rose from the opened case out in the garage when I switched the shopvac hose to “blowing” and directed a stream of cold air into the works. Whoa—back up and don't inhale!

I ordinarily do periodic degunking of my system, but we were gone so much during 2007 that I just stopped. The lesson here is that “degunking” is not just a software metaphor. Dust matters, sometimes as much as disk fragmentation and register clutter. The easiest and safest way to remove dust from a PC case is to blow it out. Don't vacuum—the snout of a vacuum hose accumulates significant static charge over a few seconds and can damage the electronics if the snout touches the mobo (or other hardware) in the wrong spots. Take the box out onto the driveway or the deck and blow air into it without touching the case. Pay particular attention to the CPU area, especially if you have a CPU fan pulling air through a heatsink. Blow air into the power supply through any vents it has, and make sure any vents in the case are clear.

Dust is a little like fiberglass fuzz in that it traps air and acts as insulating material once it gets thick enough. If you don't get the dust off your CPU, it will heat up, and if your CPU usage gets aggressive, it may heat up enough to damage the die. My CPU zone now drops to as low as 108 when the machine is idle, and hasn't gone up past 135 even during furious Dreamweaver input sessions. 30 degrees saved at the cost of two minutes with a shopvac hose—that's the power of dust.

My Antec case custom box is fairly quiet, but Antec has an even quieter case now, with larger, slower fans and a little more room inside. I've been having trouble with the audio connectors on the front case panel, and it occurs to me that if I'm going to do a case transplant, I might as well buy a new dual-core mobo—or perhaps a quad—and play around with multiprocessing. Changing out the case is pretty much the same as building a new machine, so perhaps it's time to do the research and get a hatful of new cores in the bargain. I'll let you know what I decide.