Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!ncifcrf!lhc!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <16012@smoke.brl.mil>
Date: 30 Apr 91 16:30:21 GMT
References: <7299:Apr2510:22:2091@kramden.acf.nyu.edu> <12535@dog.ee.lbl.gov> <15896:Apr2714:35:3991@kramden.acf.nyu.edu>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 14

In article <15896:Apr2714:35:3991@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
-Does anyone agree with Jef that it's ``disgusting'' to see
-	Message from operator@kramden on ttyp7 at 10:24 ...
-	operator: this is where the text goes
-	operator: and so on
-	End of message from operator@kramden on ttyp7 at 10:25

I would say rather that it's overengineered for the purpose.

-3. Do people think it's a problem that ``write'' can flood a terminal
-with output before the recipient has a chance to react?

I would put the burden of terminal display management on the terminal,
not on the "write" utility (which is not in a position to do it properly).