From: s_titz@ira.uka.de (Olaf Titz) Subject: Re: TERM & XWINDOWS REMOTELY (and job control questions) Date: 19 Apr 1993 11:10:21 GMT
In article <1qt59g$46o@uniwa.uwa.edu.au> oreillym@tartarus.uwa.edu.au (Michael O'Reilly) writes:
> : Of course, in order to link with the "term" program running on the sun4
> : unix machine I have to run a terminal program (like minicom) in linux on
> : my PC. The terminal program must be running when I execute term or my
> : modem hangs up.
>
> Try either shelling out of the modem program to run term, or
> suspending it (control-Z or some such). The comms program can be
> alive, but NOT running.
Shelling out doesn't always suffice. A method that has proven to work
is: Use kermit (better than minicom for following reasons: (a)
non-bugged terminal control and (b) can be controlled with scripts) to
control your modem and log in, after running the host term type the
kermit escape character and then Z (or give kermit the 'suspend'
command), which will cause kermit to SIGTSTP itself. Shelling out
(with !) from kermit will cause kermit to eat characters from the
line, making the term connection unusable.
I'm working on shell/kermit scripts to make the process of firing up local
and remote term servers automatic, but have run into the problem that
kermit's suspend does always suspend calling scripts too, when using
bash (is this an error in bash?), so I'm trying it with tcsh. First
results look better...
Olaf
--
olaf titz o olaf@bigred.ka.sub.org voice@49-721-60439
comp.sc.student _>\ _ s_titz@ira.uka.de praetorius@irc
karlsruhe germany (_)<(_) uknf@dkauni2.bitnet happy linux user
what good is a photograph of you? everytime i look at it it makes me feel blue