<br><br><div class="gmail_quote">On Sun, Dec 28, 2008 at 8:14 PM, Craig Huff <span dir="ltr"><<a href="mailto:huffcslists@gmail.com">huffcslists@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Long story / short: I am still running MythTV 0.20.x on FC6 and/or<br>
CentOS 5.x for various reasons.<br>
<br>
If I temporarily add another hard drive to one of my working systems,<br>
partition it appropriately, and use "dump | restore" to get a<br>
duplicate disk (and then figure out how to put the MBR on it and fix<br>
issues with Fedora's predilection to tie everything to the disk UID<br>
instead of the partition name, such as /dev/hda4) is there a decent<br>
chance it will work as a system disk for another system with a<br>
different mobo, but with the same cpu family -- meaning something like<br>
AMD Athlon - AMD Athlon, or Intel Core 2 Duo - Intel Core 2 Duo?<br>
</blockquote><div><br>CPU family is more generic than that - there's a 686 kernel which runs on all 32-bit systems from a PII up, and a 64-bit kernel which runs on both AMD and Intel 64-bit CPUs.<br><br>Of more concern is the hard drive controller - typically the initial ramdisk is set up to work with the controller chipset on the system, and a different system may use a different controller, resulting in a kernel panic on bootup.<br>
<br>To deal with this, after booting up with a rescue disk and running grub-install (typically "grub-install /dev/sda"), I rebuild the initial ramdisk with "mkinitrd -f /boot/initrd-KERNELVERSION KERNELVERSION", where KERNELVERSION is the full string after "vmlinuz-" in the /boot directory (whichever kernel the grub boot menu defaults to, of course).<br>
</div></div><br>Calvin<br>