[mythtv-users] 0.25 mpeg2 lossless transcoding works again! hallelujah! except...

[Michael T. Dean]

On 03/15/2012 07:08 AM, Mike Perkins wrote:
> On 14/03/12 22:17, Michael T. Dean wrote:
>> On 03/14/2012 05:53 PM, Mike Perkins wrote:
>>> On 14/03/12 20:13, jk90090 wrote:
>>>> On 3/14/12 11:38 AM, Mike Perkins wrote:
>>>>> On 14/03/12 15:30, jk90090 wrote:
>>>>>> Moving it to mythtv-setup is the wrong direction IMHO.  I feel it's bad
>>>>>> design to move more things to that interface backend.  There really
>>>>>> should only be *one* graphical interface for Mythtv (not two!), with all
>>>>>> setup screens within it.  The mythtv-setup should be able to but run in
>>>>>> text-only mode for the very basic setup (DB setup) and then use the
>>>>>> frontend for further configuration like provider, card, channel setup,
>>>>>> etc.  Without this, you can't run a windows-less backend and that feels
>>>>>> to me like it defeats the purpose of having a split between frontend and
>>>>>> backend.  This might end up driving me crazy enough to go about adding
>>>>>> this improvement to the development tree for 0.26.
>>>>>>
>>>>> "Without this, you can't run a windows-less backend"
>>>>>
>>>>> Oh, yes you can! ssh -X or ssh -Y can do this perfectly well from any other
>>>>> host. I believe you can use vnc or other methods too. ssh is the way I've
>>>>> maintained my MBE for years, and it doesn't even have X installed.
>>>>>
>>>>> The way forward seems to be a separate web interface, which I understand is
>>>>> planned for a future release. Till then, mythtv-setup over ssh works well enough.
>>>>>
>>>> Mike, correct me if I'm wrong but I believe that still requires you to
>>>> have the Xlibs on the backend... When I say windows-less, I mean
>>>> completely devoid of X.
>>>>
>>> That's an interesting one. It seems that currently there *are* X libs on the
>>> box, although I don't run X on it at all.
>> Qt requires X libs.  MythTV requires Qt.
>>
>> X libs are approximately 10MB, installed.  If you really have a problem
>> with that, you should buy a HDD made after 1991.  :)
>>
>> And, FWIW, Qt debug build with demos and examples:  4.5.3 = 838MB; 4.6.2
>> = 999MB; 4.7.3 = 1.3GB; 4.8 = 1.3GB...
>>
>> And with that Qt 4.7.3, if you remove debugging, it's still 500MB, and
>> of that, demos are 15MB and examples are 55MB and docs are 300MB, so
>> even if you pare it down to basics, Qt 4.7.3 is still 130MB = 13 times
>> the size of X libs.  Qt 4.7.3 libs, alone, are 80MB (=8x the size of X
>> libs).
>>
>> (This is also why people shouldn't be worried about installing
>> mythfrontend on a backend-only machine or mythbackend on a frontend-only
>> machine.  See
>> http://www.gossamer-threads.com/lists/mythtv/users/507780#507780 and the
>> rest of the thread--and note that pebender, who replied that the size of
>> the binaries is "in the noise relative to the other software needed to
>> create a running distribution," is maintaining a distro specifically
>> tailored to diskless operation-- http://www.minimyth.org/ --so should
>> have a good idea of what is and is not a concern.)
>>
> Way to miss the point, Mike. And you keep bringing this up when it's not
> relevant. This is a box stuffed in a cupboard. The disks it has are plenty big
> enough to run any amount of software on. It will only ever be accessed remotely,
> so I see no point on starting up any display manager or xorg.
>
> Therefore, I don't want the disk cluttered up with unnecessary software - and by
> "cluttered up" I mean from the administrative point of view, not disk space.
> However, if I have to have the files there to make something work the way it's
> supposed to do, then I see no problem with doing that. I just hadn't remembered
> that the X software had been installed in the first place, that's all.
>
> And yes, I do use minimyth.
>
> * Incidentally, with certain Intel graphics chipsets, I can't even get my
> servers to boot without having a screen plugged in. I have to change xorg.conf
> to use the "vesa" driver which is not so tight-assed about missing hardware -
> even when I'm not running X.
>


It wasn't you who seemed to be concerned about installing X libs.  I was 
just replying that having a system, "completely devoid of X," shouldn't 
be a concern--and, in the same message, explaining why X libs were 
installed on your system.

Mike