[comp.unix.microport] Trying to use the same line to dial in and out

karl@sugar.uu.net (Karl Lehenbauer) (07/24/88)

We're trying to get Bell Tech Unix to use the same line for dial in and dial
out.  The problem is that to dial out, tty0 must be opened without modem
controls.  Otherwise, the open hangs until CD is present.  getty, on the
other hand, wants to open the device with modem controls, so it won't
initiate a login until someone connects with the modem.  Incidentally,
there is no entry in /dev for tty00 or tty01 with modem controls.  Section
7 of the sysadmin manuals has a section called ASY that says you need to
OR a 16 into the minor device number, so we mknod'ed /dev/ttym0 with this
bit set.  Does anyone believe ordinary DOS weenies are going to be able or
willing to figure this stuff out?  Anyway, the problem now is that uugetty
and uucico use different filenames for tty0, hence they don't manage to
lock each other out.  Specifically, when uucico places a call, as soon as
it gets carrier detect, uugetty will try to get the remote sytstem to log
in.  That's bad.

Shouldn't the Unix validation stuff include making sure that one can plug
modems into serial ports, especially the built-in ones, and be configured
for both dial in and dial out, as uugetty is documented to allow?  What
is the fix?
-- 
-- backups:  always in season; never out of style.
-- karl@sugar.uu.net aka uunet!sugar!karl

hack@bellboy.UUCP (Greg Hackney) (07/24/88)

In article <2332@sugar.uu.net> karl@sugar.uu.net (Karl Lehenbauer) writes:
>We're trying to get Bell Tech Unix to use the same line for dial in and dial
>out.

Karl, I have been using a port for in/out dialing on my MicroPort 386
machine for about 4 months, and it has performed flawlessly.

I'm not sure how Bell Tech compares to MicroPort, but I'll explain my
setup, and if it doesn't help you, then maybe it will help a MicroPort user...

I'm using a Hayes 2400 SmartModem, configured as follows:

AT&F	resset to factory settings
AT&T5	no remote loopback
ATQ1	no results codes
ATM0	no speaker
ATE0	no echo
ATS0=1	answer mode
AT&D3	reinitialize upon DTR transition
AT&W	save the settings

The above settings leaves the modem ready to answer a call. After an outgoing
call, the DTR transition causes it to revert back to the answer mode settings.

/etc/inittab entry:
u0:2:respawn:/usr/lib/uucp/uugetty -r tty00 2400

/usr/lib/uucp/Devices entry:
ACU tty00 - 2400 hayes
ACU tty00 - 1200 hayes

/usr/lib/uucp/Dialers entry:
hayes	=,-,	"" AT&FM0\r\c OK\r ATDT\T\r\c CONNECT

Note: When calling out, the above entry temporarily calls up
the factory default settings, which are good for dialing out
with the exception of adding M0 to turn the speaker off.

A ls -l of /dev/tty00:
crw--w--w-   1 uucp     other      3,  0 Jul 23 21:22 /dev/tty00

--
Greg Hackney
hack@bellboy.UUCP