Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!julius.cs.uiuc.edu!zaphod.mps.ohio-state.edu!ncar!gatech!bloom-beacon!eru!hagbard!sunic!mcsun!unido!wrkof!odbffm.incom.de!oli
From: oli@odbffm.incom.de (Oliver Boehmer)
Newsgroups: comp.unix.xenix.sco
Subject: Re: Does uu/ungetty force S0=1 for dial out lines?
Message-ID: <1991Jan31.070143.28223@odbffm.incom.de>
Date: 31 Jan 91 07:01:43 GMT
References: <563@twg.bc.ca> <1810@chinacat.Unicom.COM> <578@twg.bc.ca>
Lines: 21

In <578@twg.bc.ca> bill@twg.bc.ca (Bill Irwin) writes:

>chip@chinacat.Unicom.COM (Chip Rosenthal) writes:

>:The moral of the story is if you are going to put a modem on the
>:line - even if you aren't running uucp upon it - then make sure
>:there is a good Devices entry.

>I have come to the realization that the &hayes2400 entry in
>Dialers was running whenever the port was enabled.  By specifying
>the hayes1200 dialer, which doesn't set S0, the problem is gone.
wrong. The entry &hayes2400 is executed when the port is brought up to
default state, after the connection is finished. uucp executed the
hayes2400-line (w/o &) via uuchat prior to dialing. Afterwards, it executes
the &hayes-line.
oli
-- 
---------------------------------------------------------------------
Oliver Boehmer, Frankfurt, Germany    uucp:   oli@odbffm.incom.de
+49-69-331461 (voice) +49-60-308265 (12/2400)
If God is perfect, why did He create discontinuous functions?