Xref: utzoo comp.unix.microport:2966 comp.unix.questions:12159 unix-pc.general:2433
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!spdcc!rayssd!chinet!les
From: les@chinet.chi.il.us (Leslie Mikesell)
Newsgroups: comp.unix.microport,comp.unix.questions,unix-pc.general
Subject: Re: ct on SysV386 3.0Ue (Dial)
Message-ID: <7907@chinet.chi.il.us>
Date: 10 Mar 89 19:45:46 GMT
References: <584@pgthor.UUCP> <7475@killer.DALLAS.TX.US> <696@nsscb.UUCP>
Reply-To: les@chinet.chi.il.us (Leslie Mikesell)
Followup-To: comp.unix.microport
Organization: Chinet - Public Access Unix
Lines: 13

In article <696@nsscb.UUCP> rhc@nsscb.UUCP (Rick Calder) writes:

>This is how life was prior to intelligent modems, and ct worked.

>		Rick Calder, AT&T National Systems Support Center

Doesn't this imply that it is well past time to fix dial(3C) to
match reality?  That is, so it does everything HDB uucp and cu
do, like handle modem classes, TLI or STREAMS links, and per-service
setup files.  Yes, that will require changing the CALL struct to
pass the extra information (device class and calling program name).

Les Mikesell