Subject: Re: X questions: how to run x-program on other machine?
Message-ID: <1992Aug14.232337.7936@colorado.edu>
Sender: news@colorado.edu (The Daily Planet)
Nntp-Posting-Host: kinglear.cs.colorado.edu
Organization: University of Colorado at Boulder
References: <zhao.713807106@unixg.ubc.ca>
Date: Fri, 14 Aug 1992 23:23:37 GMT
Lines: 41
In article <zhao.713807106@unixg.ubc.ca> zhao@unixg.ubc.ca (Jiansheng Zhao) writes:
>Hi, there,
>I have X running, but still have some questions.
>1). I couldn't run any x-program (xrn, etc) on our university's mainframe
>unix machine, which has all those wonderful x-program. There supposed to be
>a xhost or something, or setenv DISPLAY xxx.xxx.ca:0, which I cann't figure
>out. University Computing Centre cann't help much, they were suprised to
>know I am running X on a PC under L-I-N-U-X. Is it possible to dial-in and
>run x-program from my linux-X machine?
Not yet. To run the stock X server and clients, you need to have
either a unix domain socket (local machine), or a TCP/IP socket
connection. This means you need to have IP access to the
net on which the host computer runs.
IP access may be attained through either a dirrect ethernet connection,
or via SLIP or CSLIP - Serial Line IP, or Compressed SLIP.
In order to run SLIP, both ends must be support SLIP software. Generally,
you need th sysadmin of the remote site to add you in so that they will
route packets to you.
Another possibility is setting up a bogus X server on the remote
machine as some display other than :0, and coming up with a scheme
for transmitting requests to your local clients through some propriety
scheme.
Certain vendors do this.
You might look at xmx if you are interested.
>2). In which subdirectory should I unpack those X-program sources to
>compile?
Normally, it doesn't matter, as long as you have xmkmf installed on
your system. Xmkmf will "do the right thing", setting up the
include directories, etc, as defined in your X config directory.
--
Microsoft is responsible for propogating the evils it calls DOS and Windows,
IBM for AIX (appropriately called Aches by those having to administer it), but neither is as bad as AT&T. Boycott AT&T, and let them know how you feel.
