News Group Posts

Xnest Xwindows gui

From: "Brian K. White" <brian@aljex.com>
References: <98afjj$vi8$1@rohrpostix.uta4you.at>
<3AA8E507.FC8E7D7D@omensys.com> 
Subject: Re: remote Xsco
Date: Sun, 11 Mar 2001 19:33:40 GMT


"Serge B Bromow" <serge@omensys.com> wrote in message
news:3AA8E507.FC8E7D7D@omensys.com...
> Wolf Grossi wrote:
>
> > Hi folks,
> >     I'm running a xserver on remote machine a1 and want to connet to a2
> > using X.
> > when starting "Xsco :1 -query a2" i get connected - but the loginscreen
is
> > on vt09 of the console, not on my remote machine a1.
> > whant am i doing wrong?
> > Thanks for hints,
> > Wolf
>
> Hi Wolf,
>
> Im not familiar with Xsco's options, but have found the
> following to work properly for me;
>
> Using machine a1's window manager.
>
> 1. Login to machine a1 start an x session if
> one is not already running through scologin.
>
> 2. Obtain a terminal shell and inform the Xserver
> you plan to accept X request from a2.
> Use "$ xhost a2".
>
> 3. Telnet to machine a2.
>
> 4. Execute an X app on machine a2 and it SHOULD
> display on a1.
>
> Using machine a2's window manger, desktop, etc.
>
> 1. 1 Scologin is running.
>     Enter your logon account and passwd, BUT instead
>     of pressing enter, press the F1 key. This will start
>     on X session with nothing more than scoterm running.
>     (FAIL SAFE MODE)
>
>     .2 "$xhost a2"
>
>     .3 Telnet to machine a2.
>
>     .4 Start xsession "$ startx".
>
> 2.1 No scologin.
>
>     .2 Edit or create ".startxrc" file in home directory
>     to start only "scoterm" running in foreground.
>     "exec scoterm 2>  /dev/null"
>
>     .3 Start a1's xsession. "$ startx"
>
>     .4 From scoterm on a1 "$ xhost a2"
>
>     .5 Telnet to a2.
>
>     .6 On a2, "$startx"
>
> As usual, Im sure there are another 100 ways
> to satisfy your request. This is just one in the
> Unix world.
>
> NOTE: Due to incompatibilities between certain
> xservers you may or may not see anything.
> Case in point. Viewing xapps running on linux RH7/Caldera(a2)
> can be seen on OSR5(a1). The converse is not true,
> even though no errors are reported and all xservers
> and support apps seem to be running. To tired to
> find out WHY???

I run X apps on OSR5 and view them on Linux RH6.2 all the time.
also yet another method to add to above: Xnest! it's really cool.

Description of xnest and the situation it solves for me.

I have a Linux box at my desk on a LAN which accesses the internet via NAT,
through a router which is also another linux box.

I support a lot of OSR5 boxes. it's sometimes just "cool" but sometimes
almost required to be able to run the graphical sco admin utilities. In my
case the main thing that I don't know how to do manually is edit the config
files for the ns-httpd web server. and the only other way is to run netscape
locally pointing to the special admin servers on ports 615 and 620.

since my linux box is behind NAT (and no rules are set up to forward
incoming X traffic to my box) then the only place I could view remote X apps
on is the linux router box.

Xnest lets me do that from my desk.

I start x on my desk, then...

telnet linux-router-LAN-IP
Xnest &
export DISPLAY=:0
xterm
xhost remote-osr5-machine
telnet remote-osr5-machine
DISPLAY=linux-router-WAN-IP:0 ;export DISPLAY
PATH=$PATH:/usr/bin/X11 ;export PATH
scosession

This gives you the whole normal sco x desktop in a window.
personally, I preffer to run a local window manager on the same machine
Xnest is running on (the linux router) instead of running a window manager
on the remote machine and displaying it locally. so I do instead...

telnet linux-router-LAN-IP
Xnest &
export DISPLAY=:0
icewm (or fvwm or kde or enlightenment or gnome...)
open an xterm in the Xnest window using the window manager buttons or menus
xhost remote-osr5-machine
telnet remote-osr5-machine
DISPLAY=linux-router-WAN-IP:0 ;export DISPLAY
PATH=$PATH:/usr/bin/X11 ;export PATH
scoadmin


if you want to eliminate some harmless error messages when running sco
graphical apps remotely (regardless of Xnest), append this to your
/usr/X11R6/lib/X11/rgb.txt on linux boxes. (in the above example, it needs
to be on the linux router instead of the local desk linux box.)

save this as rgb.sco, the cat rgb.sco >>rgb.txt

!
! Special rgb.txt entries for SCO OSR 5 gui administration utilities
!
  0   0   0    scoForeground
210  70  70    scoHighlight
220 220 220    scoTopShadow
180 180 190    scoBackground
200 200 210    scoActiveBackground
  0   0  64    scoActiveForeground
230 230 230    scoActiveTopShadow
190 210 190    scoAltBackground

Comments?

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.