To what end? Personally, I see no use for it.lofty69 wrote:Come on Pablo... you know you want to
I understand the use of having frontend functionality in MiniMyth. It can reduce noise next to the television (this was my original interest in MiniMyth). It makes testing new versions of somewhat hit-or-miss software (e.g. NVIDIA drivers and video decoders) upgrades easier because it makes rollbacks easier.
I understand the use of having (slave) backend functionality in MiniMyth. It opens up more PCI slots. It allows the firewire-enabled cable box to be next to the television.
However, I do not understand the use of having master backend functionality in MiniMyth. MythTV require storage for both the database and content. As such, I do not see reason not to run the master backend on the device with the storage (in my case it is my home server). With the possible exceptions of MythTV (and therefore Qt) and V4L versions, I have had no reason to upgrade my master backend system. I continue to run RHEL5.x (actually a community created compatible version) with ATrpms packages for the MythTV (and therefore Qt) and V4L updates. Because, this server is my DNS, DHCP, SMB/CIFS, build and content server, having as much software as possible staying at the same version is preferred.
- Posts: 168
- Joined: Fri Mar 02, 2007 5:46 pm
- Location: Watching Mythtv via Minimyth
Having a minimyth style backend that boots off an SSD or CF and can be updated quickly and easily is my vision of the perfect myth system.
I really should have put a on my first post as I really said this half in jest (I'd hate to think how much time you spend as it is with minimyth alone).
rrajagopal, sounds like what you're doing is very interesting, I like the idea of "plug-in app" type functionality.