I want to use a serial monitor program. After searched google, I found
two: serialmon and serlook, but the 'serialmon' seems too old and can
not run on my slack 12.0, on the other hand, serlook looks moderm but
I requires X. Since I need to run the program in a server without X,
so I need a monitor tool doesn't require X. Do you have any suggest?
Thanks.
-
narke
Is that server the only machine on the networ? Otherwise you can log onto
that server from another machine with X and start the program on the
server displaying its windows over the network on the machine with X.
Something like this:
my_client> xhost +my_server
my_client> telnet my_server
my_server> export DISPLAY=my_client:0
my_server> /usr/local/bin/the_X_program &
Or, even better, use ssh to tunnel X:
my_client> ssh -Y my_server
my_server> /usr/local/bin/the_X_program &
regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc3(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost
Ok, I will tried this method. But other machine on the local networks
are windows. I got cygwin, I will try.
There are X servers* for windows also that you can install. CygwinX is one
free example, Xming is another free example. They can both be used
together with putty which is an ssh program for Windows.
regards Henrik
*) The word server might sound a bit odd when it comes to X. An X server
is a program that serves other programs with keyboard, mouse and display.
So the X server is usually running on a network client from where you log
in to a network server to start a program. This program on the network
server connects to the X server on your network client to show its windows.
> The word server might sound a bit odd when it comes to X. An X
> server is a program that serves other programs with keyboard,
> mouse and display. So the X server is usually running on a
> network client from where you log in to a network server to
> start a program. This program on the network server connects to
> the X server on your network client to show its windows.
This is a great explanation, thanks! I've always struggled to
wrap my mind around the client/server concept as it relates to an
x window process, and this helps a lot.
--
Theodore (Ted) Heise <th...@heise.nu> Bloomington, IN, USA