[mythtv-users] Centos 7 and mythtv

[Rob Verduijn]

2016-08-20 13:14 GMT+02:00 Jim Abernathy <jfabernathy at outlook.com>:

>
>
> On 08/20/2016 05:14 AM, John Pilkington wrote:
>
>> On 20/08/16 03:46, James Abernathy wrote:
>>
>>> Since I’m not getting anything figured out on Ubuntu 16.04.1 LTS as far
>>> as a stable display on my monitor/TV, I’m testing other long-term solutions
>>> for my Mythtv system.
>>>
>>> I installed Centos 7 today and got mythtv 0.27.4(v0.27-e4f65c8) working
>>> and the system and TV display are very stable.  This solution is good until
>>> 2020 for full updates and 2024 for limited updates.
>>>
>>> So my question is what about 0.28?  Is that going to be supported on
>>> Centos 7?
>>>
>>> I installed using the mythtv instructions for RHEL/Centos and then used
>>> the Mythtv Fedora instructions for configuration. It’s a little more work
>>> than Mythbuntu, but I figured it out. There was no mention of 0.28 in any
>>> of that information.
>>>
>>> Jim A
>>>
>>
>> I've been running 0.28-fixes under SL7 for some time, currently from a
>> 'mock' rebuild under f23 of the rpmfusion srpm.  I don't use a lot of the
>> mythtv features on offer.  The only changes I have noted are:
>>
>> - for el7: replace python2-mysql by mysql-connector-python
>> - remove frontend requirement for mesa-vdpau-drivers
>>
>> and I imagine that the second wouldn't suit everyone.
>>
>> I also have builds of 0.29-pre.  The one for f23 runs well, but I haven't
>> yet felt the need to install its equivalent on the SL7 box.
>>
>> I have no idea what might eventually be available as packages for el7,
>> but my build uses stuff from nux-dextop, which doesn't seem to be a
>> particularly active repo.
>>
>> John P
>>
>> Thanks for your comments.
>
> It looks like there is no perfect solution for me.  I spend a lot of time
> getting my Mythtv system right then leaving it alone and just using it
> without a care for years. I'm in that time of rebuilding so I want to get
> it right.
>
> Overall Ubuntu/mythbuntu 14.04 is the most stable for me right now and
> it's current enough to support the latest hardware I have and the oldest.
> Mythtv 0.27 with the features I use is the most stable.
>
> I can't use Ubuntu 16.04 because it won't work on my TV/AV Receiver combo.
> (I think it's Xorg 1.18.3 related)
> I can't use Mythtv 0.28 because of the bug in mythtranscode that I
> reported a while back.
>
> I can't rebuild for a year once the fall TV season starts.  Right now
> there's nothing to record, so I can rebuild the system daily, at least
> until happy hour starts :-)
>
> Jim A
>
>
>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>


Hi,

I've also been running mythtv on centos 7 for some time now.
When 0.28 was released I was a bit miffed because there was no repo that
contained the rpm's available.
Also the qt5 requirement was a bit of a challenge.

I solved it by installing mythtv into a fedora 28 docker container on the
centos 7.2 host.

This solved a lot of problems for me.
* quite a lot of rpms that in my view should not be instaled on a server
have been removed since they are installed in the container (cleaner server
config)
* it's now in an isolated container again which makes a far better security
solution than running it directly on a server backend
* it's a lot easier to allow a container access to a pci-card then to share
it via passthrough to a vm ( most pci cards can't deal with this including
mine)
* Rebuilding a docker container with a docker file when there are updates
is really easy.
* the mariadb runs in a dedicated mariadb container.
* cronjobs are started on the centos host with the 'container exec' command
which runs them as the mythuser in the mythtvbackend container.

There are also drawbacks.
* running mythtv setup is a pain but not impossible (I created a dedicated
container for this that I only build when needed which is almost never)
* database schema updates are a challenge too (waiting for lock ends with a
fail),
  for now I did a temporary mariadb install on my frontend to deal with
this (import old db from backend, upgrade, export new db to backend)
  I removed it once this was done. I'm still pondering what the best
solution is for this (I'm tinking of merging it with the mythsetup
container)
* it creates a rather large container
* I still need to create a container for the mythweb interface
* Ofcourse this is complete f#@$-up of the container principle, but it
works for me :-) (and was a nice learing experience)

Cheers
Rob Verduijn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160820/ceb80dc6/attachment.html>