<br><br><div class="gmail_quote">On 3 July 2010 03:18, Christian Szpilfogel <span dir="ltr"><<a href="mailto:chrisznews4@rogers.com">chrisznews4@rogers.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On 02/07/2010 3:18 PM, Brian Wood wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On Friday, July 02, 2010 12:44:49 pm Jason Ward wrote:<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Since Mythbyntu describes itself as a stripped down system specifically to<br>
run MythTV I had assumed it was indeed an appliance distro.<br>
<br>
I keep hearing people say they run their back ends as VM's, how do you do<br>
that? I though specialised hardware (like turners) were not avialable<br>
inside a VM?<br>
<br>
</blockquote></blockquote></div>
Tuners can be accessed per Brian's commented below. Setting up myth as a guest in a VM is trivial once you have a VM environment going. The best part of a VM is the snapshot ability where before any major change you can make a snapshot of the existing image and if all hell breaks loose, you can revert to it. For example, database mods, code mods, updates, etc. It has saved my bacon more than once. The master backend is the most important one to virtualize as it is the heart of the system.<div class="im">
<br></div></blockquote><div>It makes me wonder if MythTV could be distributed as a ready made virtual appliance.<br></div></div>