[mythtv-users] mythmote App and minimyth

[Raymond Wagner]

On 8/16/2012 12:52, Michael T. Dean wrote:
> On 08/16/2012 12:12 PM, Mike Perkins wrote:
>> On 16/08/12 16:05, Paul Gardiner wrote:
>>> On 16/08/2012 15:42, Mike Perkins wrote:
>>>> On 16/08/12 08:22, Paul Gardiner wrote:
>>>>> On 16/08/2012 03:32, Raymond Wagner wrote:
>>>>>> If MiniMyth actually does not provide a copy of mythtv-setup to allow
>>>>>> users to blank that setting and allow mythfrontend to listen
>>>>>> everywhere,
>>>>>> then this is a fine example of why not including applications is a
>>>>>> terrible design choice.  I realize it is designed to take up a
>>>>>> minimum
>>>>>> of storage, but mythtv-setup is all of 360KB.
>>>>>
>>>>> So this living-room appliance needs settings made that cannot be
>>>>> performed though it's usual interface? Someone has to access the
>>>>> command line and provoke the machine into displaying mythtv-setup
>>>>> in place of mythfrontend briefly to make the configuration change
>>>>> and then provoke it into redisplaying mythfrontend? That doesn't
>>>>> sound like an ideal design either. Or should minimyth provide a normal
>>>>> desktop from which the user had to start mythfrontend each time
>>>>> the machine is booted. Again not a great design.
>>>>>
>>>> Er, no. To access the backend setup parameters, provided that the slave
>>>> backend is activated in the tftpboot config file, there's a menu option
>>>> available once the front end has booted up. This allows you to stop the
>>>> backend, run mythtv-setup and restart the backend.
>>>
>>> Oh ok, a neat feature, but then that means you have to run a possibly,
>>> otherwise unnecessary slave backend to be able to set a frontend
>>> setting. I wasn't intending to criticise mimimyth
>>> with my comment. I was more trying to rebuff the "not including
>>> apps is a terrible design choice" comment, suggesting that the need
>>> for the app is more the problem.
>>>
>> I would rather suggest that this indicates that this particular
>> setting is in the wrong place.
>>
>> It's much like having to fire up the front end (on the master backend
>> that lives in a cupboard) in order to select a theme so that you can
>> then shut it down in order to set up the backend properly... the
>> default Terra theme is unusable (IMHO).
>
> You simply have to run mythtv-setup, the setup program for MythTV, to
> set the appropriate setting.  Note that it's not called
> mythbackend-setup...

More correctly, you simply don't run mythtv-setup.  The default 
parameter for that setting is blank, which means a dedicated frontend 
would automatically listen on all available private IP addresses, 
private addresses being the 10.xxx, 172.xxx, and 192.xxx addresses.

As stated on the referenced Wiki page, the frontend will only listen on 
127.0.0.1 if mythtv-setup has been run, and the default value for that 
configuration field is stored in the database.  It will similarly only 
listen there, or the address configured, if the user or installer has 
otherwise manually configured that address in the database independent 
of mythtv-setup.  Either way, the user has forced mythfrontend to only 
be available there.

There is a third possibility, the system is booting up and running 
mythfrontend before the network is available.  There are some problems 
I've heard where people are running systems on wireless networks, using 
Network Manager to configure the network and grab an IP address only 
after the UI has come up.  Of course the solution there is to set the 
wireless keys as global, or use some tool that doesn't require a GUI, or 
better yet just run wires...