Path: utzoo!utgpu!news-server.csri.toronto.edu!utcs.toronto.edu!cks
Newsgroups: comp.unix.wizards
From: cks@hawkwind.utcs.toronto.edu (Chris Siebenmann)
Subject: Re: POSIX bashing
Message-ID: <1991Apr3.200700.19802@jarvis.csri.toronto.edu>
Organization: Ziebmef home away from home
References: <3419@unisoft.UUCP> <5980071@hpfcdc.HP.COM> <3446@unisoft.UUCP> <15621@smoke.brl.mil> <70319@brunix.UUCP> <1991Apr2.032733.26365@jarvis.csri.toronto.edu> <70568@brunix.UUCP>
Date: 4 Apr 91 01:07:00 GMT
Lines: 23

cgy@cs.brown.edu (Curtis Yarvin) writes:
| Certainly; but bear in mind that all these front ends use the "pty"
| driver, which is a bletcherous hack*, kludged in to get around the
| problems that cooked mode causes.

 My favorite frontend, the terminal-emulator based one, needs a pty
anyways to talk to my shell; it's common these days for the method
people use to access their machines to need at least one pty. I also
think that many of the bletcherousnesses of ptys would probably go away
if they were reimplemented using something general like stream
connections.

 Whether or not ptys and streams are a bletcherous hack depends on your
views on the desirability of having different sorts of tty modes
around, and how much you want to start adding such semantics to pipes.
Personally, I think they're quite usefull, and can be expressed and
used in elegant ways.

--
		V9: the kernel where you can do
			fgrep <something> */*.[ch]
		and not get "Arguments too long".
cks@hawkwind.utcs.toronto.edu	           ...!{utgpu,utzoo,watmath}!utgpu!cks