From: dmarcher@acsu.buffalo.edu (Dave Archer) Subject: Re: Starting term from kermit?? Date: Wed, 11 Aug 1993 01:53:58 GMT
In article <18513@blue.cis.pitt.edu> hahn@neurocog.lrdc.pitt.edu (Mark Hahn) writes:
>> > !term </dev/[modem_port] >/dev/[modem_port] [options]
>
>that's fine for all you with plenty of ram. me, I don't want two copies of
>kermit hanging around while I'm using term. thus, I set my modem "&d0"
>so it won't hup when I exit kermit. I start term in the obvious way.
Actually, there's a way both of you can be happy. You
merely use kermit's ! to start term, but you put it in the
background, then the next line of the kermit script quits
kermit. Since kermit doesn't quit until after term's
running, the modem won't hang up, and you don't have to
disable the modem from hanging up other times when it's
supposed to.
Here's the kermit login script that I use to start term.
Obviously the login sequence is greatly different for
people using other systems, but the last few lines are what
i'm talking about here.
;do some odd stuff so we'll get response codes so dial can
;work, i do it this way due to the getty i run.
script ~w1~0 ATM0&D3Q0~r ~w2OK ~0
pause 1
set dial display on
:dodial
dial T6456600
;dial and dial and dial until we connect.
if NOT SUCCESS goto dodial
output k\13
;login to xyplex
script ~w1~0 ~r ~w9name>~s dmarcher
script UBNET> ~0
;login to lictor (me no like autarch)
script ~0 c~slictor ogin: dmarcher word: passwd_goes_here
;wait for my prompt (i run bash, so it's a $)
script ~w60$ ~0
;start term on lictor
output term\13
;give lictor some slack to start term
pause 1
;run term in the bg (again, this is bash, 2> won't work for *csh weenies)
! term < /dev/modem > /dev/modem 2> /tmp/term.log &
;bye bye kermit
quit
This `problem' seems to pop up every few months, so save
this script and feel free to throw it at anyone asking
about this in the future.