# losetup /dev/loop0 /path/to/diskimage
# fdisk -l /dev/loop0
(example)
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 * 1 1044 8385898+ c W95 FAT32 (LBA)
/dev/sdb2 1045 19457 147902422+ 83 Linux

suppose you want to mount the partition on sdb2, the offset for that
would be 8225280 * 1045 = 8595417600.

detach the disk image
# losetup -d /dev/loop0
and setup the loop for the partiion
# losetup -o8595417600 /dev/loop0 /path/to/diskimage
and mount it
# mount -t fstype /dev/loop0 /path/to/mountdir

FSDB
Scrounge-ntfs
Photorec can recover photo data

Document I followed to get MythTV Installed and ivtv modules working using this document. This document has the package repository used: http://packman.iu-bremen.de/suse/10.2.

This command worked to get the ivtv driver to load:
sudo rpm -Uhv http://jarpack.com/suse/noarch/ivtv-firmware-0.1-1.noarch.rpm

ivtv-fb loaded without issues. It took a bit of googling to find a ivtv driver for xorg. Here it is:
http://www.hellion.org.uk/ivtv/debian/ivtvdev_drv.so~i386

LIRC was the next issue. Here is a bug with LIRC in SuSE 10.2 that prevents /dev/lirc and /dev/lirc0 from being created.
I compiled up the source and was able to copy just the kernel module to fix it.
cp drivers/lirc_i2c/lirc_i2c.ko /lib/modules/2.6.18.2-34-default/updates/lirc_i2c

The problem came about due to spam sent to the ale-* administrative addresses. Each time a spammer sent an email to that list, it would add an entry to the hold_and_cmd_autoresponses variable in the config.pck file. Every time python needs to access the ale config, it had to decrypt the config.pck file which uses lots of CPU.

The solution is to overwrite that vaiable with a null. Its possible doing this could break someone trying to subscribe to the list, but eh, its a free list, they can re-try.

Create a file with the following in it:

hold_and_cmd_autoresponses={}
then run the following command from your mailman root:

bin/config_list -i /tmp/foo ale

/tmp/foo is the file I created and ale is the list I needed to fix. It dropped my 50M config.pck to 1.8M and my load issues have gone down dramatically.

• What is WordPress
• The joys of Plugins
• antispam captcha
• spell check
• post rankings
• Firestats
• iCal
• Database management
• WP-phpMyAdmin
• Database Backup
• The joys of Themes
• Database nitty-gritty
• How WP can help with your meglamanical schemes
• Websites:
• http://www.ale.org
• http://www.gwinnettgop.org
• http://www.gopliberty.org
• Blogs:
• http://www.vitalpowers.com/blog
• http://www.chrisfarris.com/geeklog
• Advanced stuff:
• http://www.georgialegislativewatch.com/

http://packman.iu-bremen.de/suse/10.2

I had to manually alter the recording tables to copy the data from the old system to the new database.

The following query was used to compare settings from the old settings table and the new settings table:
select mythconverg.settings.value, mythconverg.settings.data, mythOLD.settings.data from mythconverg.settings, mythOLD.settings WHERE mythconverg.settings.value=mythOLD.settings.value AND mythconverg.settings.data != mythOLD.settings.data INTO OUTFILE '/tmp/setting.diff';