Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!samsung!uunet!jwt!john
From: john@jwt.UUCP (John Temples)
Newsgroups: comp.unix.sysv386
Subject: Re: UUCP connection for Esix
Message-ID: <1991Jan6.161044.13555@jwt.UUCP>
Date: 6 Jan 91 16:10:44 GMT
References: <1991Jan5.200248.19487@unixland.uucp> <1991Jan5.223542.19285@isis.cs.du.edu> <1991Jan06.025812.103@nstar.rn.com>
Organization: Private System -- Orlando, FL
Lines: 16

In article <1991Jan06.025812.103@nstar.rn.com> larry@nstar.rn.com (Larry Snyder) writes:
>dkessner@isis.cs.du.edu (David D. Kessner) writes:
>
>>What is this FAS thing anyway??
>
>FAS is a replacement serial driver for 386 based Unix (3.2) that
>works correctly.

FAS isn't absolutely necessary for ESIX, since the ESIX driver works
fine at high speeds, handles the 16550, has hardware flow control,
and handles bidirectional modem access correctly.  But FAS has two
benefits over the ESIX driver: it uses less CPU time, and it supports
a non-blocking dial-out device with modem control.  The latter will
cause a dial-out program to get SIGHUP when carrier is lost.
-- 
John W. Temples -- john@jwt.UUCP (uunet!jwt!john)