Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - eloy

Pages: 1 [2]
They are taking considerable space. Can I remove them after an update without any ill effects?

Developers / Is it possible to delete device templates?
« on: September 06, 2007, 05:19:58 pm »
In the process of trying to get to work a Generic Serial Device I ended up with several device templates that aren't used. Is it possible to delete them? I don't see a way of doing it through the GUI but perhaps this can be done by issuing a direct SQL DELETE statement? Has anyone done this before, and if so, what are the tables that need to be touched?



Users / Re: LinuxMCE in existing MythTV and Asterisk environment
« on: August 25, 2007, 03:21:17 am »
You will need to have Asterisk on you Core, but you can copy your config files over and use them directly. I did that once and then I decided to use the LinuxMCE standard way as LinuxMCE keeps a lot of configuration inforation in its databases that it needs to do some of the cooler things. This was a disruiption in service, but it's the best way really.

Yeah, this is definitely an option. A couple of days of service interruption is not a big deal. I was more worried about extended instability. My only concern is that the version of Asterisk in Ubuntu Feisty is the old 1.2.x series, and the one I am currently using is 1.4.x from Debian unstable. Asterisk configuration files are not backward-compatible so I'd need to redo my Asterisk config. (and I spent some time fixing some things in the 1.2 to 1.4 migration.)

Ubuntu Gutsy does have Asterisk 1.4.x. Guess one option is to try APT pinning to get Asterisk 1.4.x after doing the LinuxMCE initial install.

As for MythTV... I wish... This is actually a big problem for me. It seems LinuxMCE uses an outdated version of MythTV and is incompatible with the newer releases. However, if your backend is the same version then you can use your existing Myth system. Although you should move the database to the Core.

Indeed, this is a big problem.


I almost forgot... the Kubuntu thing is being discussed in the Developer forum. I still don't understand it's rational...

Oh, cool. I'll check it out; thanks for the info.



Users / LinuxMCE in existing MythTV and Asterisk environment
« on: August 24, 2007, 09:06:24 am »
Hello all,

I already have a MythTV and Asterisk environment (one server for each). I'd like to try LinuxMCE but I was wondering if it is possible to configure it to use my existing Myth and Asterisk setup instead of configuring everything again in the new LinuxMCE install. Couple of reasons I want to do this:

- Both Myth and Asterisk are being used in production - both are completely stable, the whole family uses Myth, and I use a VoIP provided that is connected to my Asterisk server. Moving these services to the new LinuxMCE install would cause unwanted disruption and likely introduce instabilities.

- The Myth server is both the backend and the main frontend. Most likely the LinuxMCE machine will be a different one (in a different room), which will require moving all the TV capture hardware (I've got three tuners) to the LinuxMCE machine. Major pain.

- Both machines being used for Myth and Asterisk provide other services as well (web servers, e-mail, spam scanning, backup services, etc.) It's not easy for me to bring them down, netboot, and use them for LinuxMCE.

Has anyone being able to re-use an existing Asterisk and Myth setup with LinuxMCE? I don't care if this is not achievable through an idiot-proof installation - my stuff is running on Debian unstable and I've been using Debian for 10 years, so I don't mind editing configuration files and tweaking the system manually.

And while we are on the topic, is Kubuntu really a requirement? I mean, is it not possible to install the Debian's KDE packages and on top of that the LinuxMCE packages? I think that making LinuxMCE distribution-agnostic would be extremely cool. Anyone working on this?

Thanks for any comments on these topics.



Pages: 1 [2]