Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!hobbes.physics.uiowa.edu!news.iastate.edu!sharkey!fmsrl7!wehr
From: wehr@fmsrl7.UUCP (Bruce Wehr )
Newsgroups: comp.sys.hp
Subject: Re: Callback on HP 9000/380
Message-ID: <44044@fmsrl7.UUCP>
Date: 20 Jun 91 12:00:49 GMT
References: <843@utrcu1.UUCP>
Organization: Ford Motor Company, Scientific Research Labs, Dearborn, MI
Lines: 35

hendri@math.utwente.nl (Hendri Hondorp) writes:
> a.	uugetty is running on the modem-port tty09 (via inittab):
> crw--w--w-   1 uucp     users      1 0x090010 Jun 17 15:49 /dev/tty09
> 
> 	Ct uses cua09 or cul09:
> crw-rw-rw-   1 root     other      1 0x090011 Jun 17 13:24 /dev/cua09
> crw-rw-rw-   1 root     other      1 0x090011 Jun 17 14:45 /dev/cul09
> 
> My questions are:
> a.	why can't we use uugetty and ct ? Uugetty is simular to getty
> 	except that uugetty supports using the line in two-directions.
> 	(in/outcall).

    I'm not sure why uugetty doesn't work, but I *do* know that it's
    unnecessary. HP's terminal driver has port access interlock
    mechanisms built in to handle shared incoming and outgoing
    processes. Bit 0 of the minor number controls this, and you have
    them configured correctly (what's bit 4 for, BTW?).

> b.	Are there more HP 9000/3xx systems configured with a callback 
> 	procedure and how did they do it ?

    At my previous position, I configured a 9000/375 just the way you
    did (with a TrailBlazer), except we just used a regular getty.
    Users would just use ct directly - some created a shell script with
    all their appropriate parameters (one user named his et - for
    'phone home' :-)

    Anyway, I hope this helps.

-- 
               Bruce Wehr (wehr%dptc.decnet@srlvx0.srl.ford.com)
                (..!uunet!srlvx0.srl.ford.com!wehr%dptc.decnet)
              Ford Motor Company - Engineering Technology Services
     P.O. Box 2053, Room 1153, Dearborn, Michigan 48121-2053 (313)337-5304