Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site kitty.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!rochester!rocksanne!sunybcs!kitty!peter
From: peter@kitty.UUCP (Peter DaSilva)
Newsgroups: net.unix-wizards,net.flame
Subject: Re: Re: UNIX-WIZARDS Digest  V1#112 (NIH)
Message-ID: <208@kitty.UUCP>
Date: Thu, 1-Aug-85 10:42:05 EDT
Article-I.D.: kitty.208
Posted: Thu Aug  1 10:42:05 1985
Date-Received: Sat, 3-Aug-85 05:54:14 EDT
References: <64@brl-tgr.ARPA> <311@baylor.UUCP> <143@ho95e.UUCP>
Organization: Recognition Research Corp., Clarence, NY
Lines: 17
Xref: watmath net.unix-wizards:14170 net.flame:11443

> If you want to flame about how changing things is, look at
> the change from 4.1BSD to 4.2BSD!

I have never used 4.1, but apart from directory entries, I have nothing to
complain about in porting vanilla V7 stuff to 4.2. Since 4.1 is a V7
derivative, I can hardly see that the 4.1 -> 4.2 change could have created any
major incompatibilities.

The SIII system I used was a Unisoft port. It didn't require you to diddle
with MIN and TIME to set CBREAK mode. If you don't you get 4 character
granularity in reads, and they time out after 2.8 seconds. This broke several
programs I was trying to maintain on a system that was converted from SIII to
SV. I still haven't gotten Xmodem to work reliably again (though I must
admit I haven't spent a great deal of time working on it lately).

Can you say "incomptibility"? The 4.2 method of handling timouts is much
better, since it ADDS a function, instead of CHANGING an existing one.