Jarod Wilson wrote:
On Wednesday 09 March 2005 19:49, James Armstrong wrote:
On Mar 9, 2005, at 9:41 PM, Jarod Wilson wrote:
On Wednesday 09 March 2005 18:21, Bryan Halter wrote:
How else are you going to run the setup utility? Until someone
writes
something like an ncurses-based setup utility, I think folks are
SOL.
[...]
Would a ncurses based mythsetup be out of the question?
That was my suggestion for a no-X, no-Qt setup util.
I run the setup program on my headless backend all the time. I just ssh
into it from my frontend and run setup. The setup program is displayed
on the frontend using X but is actually run from the backend and
modifies the backend's settings.
I know, I do the same. The question was why X and Qt even have to be on the
backend though.
When you run an X application remotely, it is the GUI output that gets
displayed at the local machine. In other words, if you ssh into the
backend from a frontend (or any *nix box) and run mythsetup, mythsetup
runs on the backend (ie it's using the backend's CPU cycles), but the
output is displayed on the frontend.
Hope this explains why you'll need X and Qt on the backend.
If you have a headless backend then
you must have a frontend running on X, unless it is on OSX then I don't
know.
Run X11 on the Mac and do the exact same thing.
Just my 2 cents worth.
|
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
