A number of people have been struggling with this so I thought I would start to document what I did to get this working. It is cumbersome but do-able. I also strongly suggest you also use the sme server as a backend and don't implement the frontend on it as i have little confidence in the security of it.
I would suggest moderate and more expert users check this out first to see if I have some errors or holes. If it's close then we can update the wiki. I just didn't want to muck it up before some sanity was applied. In particular, I would like to see if there is any minimization we can do say by removing unnecessary steps or packages.
I had to draw on many sources including: Duncan's how-to (link currently dead); the contrib wiki; mythtv.org (and it's wiki); knoppmythwiki.org; and many more that I have forgotten.
Here goes and good luck.
============
Set up repositoriesSet up atrpms per the wiki (
http://wiki.contribs.org/ATrpms) - IMPORTANT to use this method to avoid including unwanted items
Set up dag as follows:
/sbin/e-smith/db yum_repositories set dag repository BaseURL http://apt.sw.be/redhat/el4/en/i386/dag EnableGroups
1 GPGCheck 1 Name Dag-repository status disabled
expand-template /etc/yum.conf
Install a few dependencies:You will likely need the following (based on Duncan's How to). I know some are needed but have not confirmed if all are needed.I suspect some of it is only needed if you wish to load up the myth source and use their "config" tool.
yum install gcc-c++ qt qt-MySQL qt-devel ncurses-devel
yum install python-devel zlib-devel dialog subversion
Now itstall the Myth bits:** Note I had to install the ivtv-kmdl separately as the non-smp won't install if you are running in smp. I believe smp is the default for sme server.
yum install mythtv-mythweb --enablerepo=atrpms --enablerepo=dag
yum install mythtv-setup --enablerepo=atrpms --enablerepo=dag
yum install ivtv-kmdl-2.6.9-55.0.6.ELsmp-0.4.10-114.el4 --enablerepo=atrpms --enablerepo=dag
yum install ivtv --enablerepo=atrpms --enablerepo=dag
yum install mythtv-frontend --enablerepo=atrpms --enablerepo=dag
Setting up mysql:You will need to set up mysql. The required mc.sql file I would recommend you get from Mythtv's web set just to ensure it is accurate for your version. The following is over kill but you will find it there.
Download the mythtv software to a directory of your choice from:
http://www.mythtv.org/modules.php?name=DownloadsYou should just need the main load not the plugins.
if it downloads as a ".tar.tar" file then change the name to end in ".tar.bz2"
then
bunzip2 mythtv-0.20.2.tar.bz2
tar -xvf mythtv-0.20.2.tar
cd mythtv-0.20.2/database
mysql < mc.sql
Now grant access to your box and remote front ends within subnet 192.168.1 (change to suit you) to access mysql
mysql
mysql> grant all on mythconverg.* to mythtv@'192.168.1.%' identified by 'mythtv';
mysql> flush privileges;
mysql> quit
/sbin/e-smith/config setprop mysqld LocalNetworkingOnly no
/sbin/e-smith/expand-template /etc/my.cnf
service mysqld restart
From the shell window of your front end, verify that the access worked:
mysql -h smeserveraddress -u mythtv -pmythtv mythconverg
** Note smeserveraddress should be an IP address or FQDN
if you have no error then quit. If you do then it is likely a permission or grant error to be resolved.
ALMOST there!!X11 Forwarding:You need to set up X11 forwarding to another Linux machine (I targeted a CentOS release running on a virtual machine (VirtualBox) on
my XP Home machine.
X11 Forwarding is described here:
http://wiki.contribs.org/X11_Forwarding_on_SMEthen go to your shell window on another machine (which has X running) and do:
ssh -X root@smeserveraddress /usr/bin/mythtv-setup
and follow the instructions to set up your environment for the backend.
To set up Knoppmyth as front end only:I decided to use Knoppmyth as my front ends as there seems to be good support including HOW-To's to link things together.
Install Knoppmyth from "
http://www.knoppmythwiki.org/?id=KnoppmythDownloads" onto a front end PC.
Follow this HOW TO
http://www.knoppmythwiki.org/index.php?page=FrontendOnlyInstallI would also recommend defining a common file structure for your frontends and backends. I used the SME as my common file store. In theory, the next version of myth will allow you to more easily share directories but for now you will need to follow the following HOW-TO's
HOWEVER, you won't have much joy using NFS (per their suggestion) and rather than samba you may wish to consider using sshfs as described in:
http://ubuntu.wordpress.com/2005/10/28/how-to-mount-a-remote-ssh-filesystem-using-sshfs/After you make your mounts, adjust your directory structure in the myth frontend to suit your mount structure.