 |
|
|
|
|
Windows as an Xwindow
terninal. XManager - an
excellent commercial product - offers the X service. Here is a most
impressive scene of 2 desktops at 1. On the Linux server's side
Blackbox is the Window Manager and Xterm is initiated. Background
transparency at its best!
|
|
XManager acts
as an X server only. Kde Desktop (and Window Manager) and Konsole run
on the Linux server. This can be minimized or windowed (or scaled) or
full-screened. |
|
XManager has also the
multiple window management feature and the linux server runs only
applications. "Xclients" run in the Linux server, and the Xserver
runs on the Windows client. The "inversion" takes place because
all this is decribed from the application's point view instead of the
user's.
|
|
2 terminals are
logged on the same server, but do not run on the same machine. Putty
runs locally on Windows, while Xterm runs on the Linux server
communicating with XManager.
|
|
Running useful apps
in the Linux server: Here I manage my contacts through Kaddressbook
(included in the KDE suite). There are also calendars, organizers,
finance managers etc. With Windows as an Xterminal, I centralize a
bunch of jobs.
|
|
Here running the
XpkgTool updater (you've already seen it in Linux screenshots) as an
xclient from the server on the client's XServer. This riddle means that
I run the server's application on the client's graphics environment.
|
|
Graphics applications
from a Linux server on Xming XServer on Windows
7, with the SSH X11 port
forwarding option (notice the $DISPLAY parameter in Putty Terminal). Aside the
encryption benefits, the lack of "target" ip address for X clients
makes the attempt less complicated for the desktop. No port
redirecting, or additional firewall rules. But we need an ssh client
and a properly configured ssh server on the remote system.
|
|
|
