<html><body bgcolor="#FFFFFF"><div><br></div><div>On Jan 17, 2012, at 12:25 PM, Kirk Bocek <<a href="mailto:t004@kbocek.com">t004@kbocek.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span></span><span></span><span>Because the same philosophy one applies to a corporate server goes </span><br><span>doubly with a Myth box.</span><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#0023A3"><br></font></font></div></blockquote><br><div>It may not be for everyone but, for me, the solution to all of my dependency problems was to compile Myth from source. My dedicated backend runs Centos 6. My frontends run whatever best supports the hardware, usually Fedora or Ubuntu, but it could be anything since I don't have to worry about Myth package support. I just sftp the Myth tarball to the desired machine and compile it. So I never get "forced" into upgrading a working machine in order to address an issue on another. Which is the same reason I run separate frontend and backend machines.</div></body></html>