On 2013-03-24 22:18, Hans J. Albertsson wrote:
The optimum solution is for me not to have to zlogin or ssh into the
zone and start vncserver, but be able to login remotely into the zone
from anywhere within a trusted lan.
So I'd like to try to get that working nicely, just as I have Xvnc
working
The optimum solution is for me not to have to zlogin or ssh into the
zone and start vncserver, but be able to login remotely into the zone
from anywhere within a trusted lan.
So I'd like to try to get that working nicely, just as I have Xvnc
working well for remote login to the global zone of
On Sun, Mar 24, 2013 at 8:19 PM, Hans J. Albertsson
wrote:
> It should work in principle, using Xvnc and/or Xephyr in lieu of xnest. It
> doesn't, and the main problem seems to be that gdm professes to depend on
> dbus, and dbus refuses to install in an NGZ. I suppose that's reasonable.
>
> I supp
It should work in principle, using Xvnc and/or Xephyr in lieu of xnest.
It doesn't, and the main problem seems to be that gdm professes to
depend on dbus, and dbus refuses to install in an NGZ. I suppose that's
reasonable.
I suppose one might be able to fake the dbus presence, exactly how
dep
I didn't think Milan was done updating JDS. I'd assume someone is
very confused. Especially since "Update to this other piece of
software" hardly resolves the bug in what _is_ shipping.
-- Rich
___
OpenIndiana-discuss mailing list
OpenIndiana-discuss@
On Solaris 10, I used to configure my zones to run xnest as the X server
with the display directed back to the global zone. xhosts in the global
zone was configured to allow the zones access.
It worked like a charm.
I even had a linux branded zone I used for google earth. In that case I
used zlog
