Ugh. He just doesn't know what he is doing, does he?

Who is this poseur?

Who laughs at an economy in trouble?




And is this what the people that voted for him expect to get?

Two Telling Quotes..

"People tend to pay their mortgages. I don't think we are in any remote danger here. This focus on receivership, I think, is intended to create fears that aren't there." - Barney Frank (D), In a speech to the Mortgage Bankers Association

"While I favor improving oversight by our federal housing regulators to ensure safety and soundness, we cannot pass legislation that could limit Americans from owning homes and potentially harm our economy in the process." - Protesting against greater controls against lax mortgage lending, Sen. Harry Reid (D)

And we're running again, well maybe strolling or limping..

Here's an update to the situation.

I did have to rename some things in both grub.conf and /etc/fstab. Since I couldn't figure out how to get the MythDora 5 boot DVD to stop at the grub menu, I booted from a Ubunutu 6.06 LTS livecd and picked the option to boot from the 1st hard disk (I think that's what the menu item said) and it began to load MythDora from the new disk. It ran into some problems due to what I had excluded when I did the rsync copies though and somewhere there was a reference to the old LVM Volume Group name. So I rebooted to the Ubuntu livecd command prompt and used vgrename to change the name to the same one as the dead drive used. I again rebooted with the livecd and chose the option to boot from the hard disk. This time it got further into the boot process but there were still problems with missing directories (/var/run and /var/lock among others). I corrected as much of that as I could and restarted using the Ubuntu livecd. The system is now up and running with the new disk and should have recorded a show last night on the schedule. It's a good thing this was a down week for scheduled recordings.

So now I have a system that still won't boot on it's own. I'm guessing that the MBR is not what it should be since the drive will boot if I use a boot cd's grub to load it. The question is, how do I correct the MBR? On the chance that the copy of grub on the new hard disk was somehow damaged, I used yum to remove grub and reinstall it. I'm going to run another grub-install /dev/sda and see what that yields.

Well that didn't take long..

I awoke to a buzzing sound the other morning and discovered it was coming from inside the case of my newish master frontend/backed mythbox. Mythdora 5 is installed on it. It turned out to the bearing on my main 320G drive. I bought a replacement and got just about everything copied to the new 500G drive. I had both drives mounted and used the Mythdora 5 rescue mode with rsync to copy stuff across. I attempted to duplicate things as much as possible with respect to LVM2 setup, but of course I had to change the names a bit. (I used rootvg2 for the base volume group on the new drive and just made the storage partition an ext3 partition and mounted it directly.)

The problem is that Grub doesn't want to play along.

After the rsyncing was complete, I booted with into rescue mode and ran the chroot /mnt/sysimage command so that I could run grub-install. I had some trouble that seems to be related to the version of grub and it's reliance on /etc/mtab. I found an possible solution for that and finally got grub-install /dev/sda to run without error. The problem is that when I boot, the computer goes through the normal post sequence and just displays:

GRUB

And never goes into the boot sequence for Fedora.

Now I need to figure out how to get this machine back in operation without losing everying and re-installing. Although maybe it comes down to that?

New Myth hardware and Myth 0.21 finally running..

Well I finally got enough spare minutes to get off my butt and get the new MythTV hardware in place. I rebuilt my TV stand specifically so it could accommodate my largish (aging) receiver and the new (even largerish) MythTV gear. Anyway, it's quieter and much more powerful and the new changes to MythTV seem pretty nice. I have a bunch of configuration to do yet and and I have to rebuild the old machine to take over for the failed HD encoder / remote frontend machine that failed. That's another reason why I just had to get this new box into position; I'm down to a single encoder and that doesn't make for much flexibility in scheduling. Plus, all the network shows we watch are broadcast in HD and that is a much better viewing experience than down-converted 480i HD that I get from the S-Video output of my DirecTV rx feeding my PVR-250 in my master backend / frontend.

I'll post some images of the new home once I get channel changing and the old schedules sorted out - I'm having an issue where the new Mythbox has forgotten all most of the Lost episodes that we've recorded in the past. For channel changing, I'm hoping to return to using the USB->USB trick that I used in the past so that I have a direct connection between the new Mythbox and the DirecTV box.

MintyBoost!

I bought a MintyBoost kit from Adafruit because I've got so many devices that charge via some sort of USB cable (4 different phones, multiple Sansa e200's, etc.) I meant to have my 2 daughters help me solder up the circuit board part so they could put their electric shop skills to good use. (See included Mr. Blurry Cam photos) But I just couldn't wait! Sorry girls.

The device can output up to 500ma at 5v so it will charge devices that my lame car USB charging adapter won't / doesn't. Apparently there is a low power USB spec that will output up to 100ma of current and a newer higher output spec.

I've included an action shot of the charger attached my Sansa e260 (booted into Sansa's firmware, which I only use for transferring files since my current version of Rockbox doesn't support full USB functionality yet). If you look closely in the lower left of the screen, you'll see the charge indicator on.

I really expect I'll get some use out of this for my T-Mobile G1 which is a big battery pig if you turn on all the wizzy extras like satellite tracking. A pair of recent NiMH AA batteries have about 2500ma capacity so should be able to charge up the G1's 1100ma pack at least a couple of times before they drop too low to push any more electrons over the USB charge cable.