Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!raybed2!rayssd!anomaly!mpd
From: mpd@anomaly.SBS.COM (Michael P. Deignan)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: SCO TCP/IP SLIP
Message-ID: <1991Mar31.053555.17192@anomaly.SBS.COM>
Date: 31 Mar 91 05:35:55 GMT
References: <5@vlink01.UUCP> <1991Mar22.075036.846@jadpc.cts.com> <1991Mar23.193818.19219@anomaly.SBS.COM> <1991Mar27.164439.5262@robobar.co.uk>
Organization: Small Business Systems, Inc., Esmond, RI  02917
Lines: 29

In comp.protocols.tcp-ip you write:

>I strongly urge you to reconsider this.  Xenix/Unix is not designed to
>be particularly efficient as a comms box OS, and thus, you will render
>that poor ole' xenix box in the middle unuseable for anything.  In terms
>of context switches alone, its CPU will be swamped.  Consider instead:

{suggestion list deleted...}

Sounds like good suggestions. Good thing I'm not planning on "expansion"
until later on down the line. Right now, I'm only working on implementing

	SCO XENIX --> dialup SLIP --> JvNCnet

Of course, It would be preferable to just run an Ethernet connection to
JvNCnet, unfortunately my measly paycheck won't allow the costs associated
with that type of connection.

MD
-- 
--  Michael P. Deignan                      / Since I *OWN* SBS.COM,
--  Domain: mpd@anomaly.sbs.com            /  These Opinions Generally
--    UUCP: ...!uunet!rayssd!anomaly!mpd  /   Represent The Opinions Of
-- Telebit: +1 401 455 0347              /    My Company...
-- 
--  Michael P. Deignan                      / Since I *OWN* SBS.COM,
--  Domain: mpd@anomaly.sbs.com            /  These Opinions Generally
--    UUCP: ...!uunet!rayssd!anomaly!mpd  /   Represent The Opinions Of
-- Telebit: +1 401 455 0347              /    My Company...