On 9/4/06, Nick Rout <[EMAIL PROTECTED]> wrote:
Frequent updating of myth machines is a mistake in my humble experience. get it right, then stop! For this reason i moved from gentoo to knoppmyth for my myth box. Never been happier.
Nick, Who said 'frequent'? I more or less agree, and I appreciate all your help in the past, but this time your comment isn't directly helpful. (As a Gentoo user) On the other hand it does serve to create some user-oriented conversation so thanks for that. The 0.18 revision had bugs. The backend hung or shutdown Myth 3 time a week when the network got busy. (Just finished recording two jobs, just start transcoding them, started recording two more and was being accessed by a couple of frontend machines all at the same time. This was almost guaranteed to cause the 0.18 backend to just shutdown...) The machines were running old kernels on old Gentoo profiles. When the profiles and kernels get updated then you find that the ati-drivers package doesn't work with the new kernel. Our Myth backend machine is a Gentoo desktop serving double duty. That machine needs to be updated, which then drives us to update the network, when then causes us to have to update the frontends because the Myth devs won't allow a 0.18 frontend to run with 0.19 backend. We we stuck. Bummer. Again, I'm not really complaining. The network is up and running again, but it is not as enjoyable as it used to be. While 0.19 is far more stable than 0.18, the video on my ATI-based frontend machines is really lousy to watch. No WAF or KAF at this time... I don't see how I Would have used KnoppMyth in this setup, but maybe I could have tried it on a frontend-only machine, if it had built in support for the ati-drivers I end up needing to get TV-out. Thanks, Mark -- gentoo-user@gentoo.org mailing list
