Xref: utzoo comp.unix.wizards:25389 alt.security:2433
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!samsung!munnari.oz.au!mundamutti.cs.mu.OZ.AU!kre
From: kre@cs.mu.oz.au (Robert Elz)
Newsgroups: comp.unix.wizards,alt.security
Subject: Re: BSD tty security, part 3: How to Fix It
Message-ID: <kre.673349595@mundamutti.cs.mu.OZ.AU>
Date: 4 May 91 09:33:15 GMT
References: <7299:Apr2510:22:2091@kramden.acf.nyu.edu> <12535@dog.ee.lbl.gov> <15896:Apr2714:35:3991@kramden.acf.nyu.edu> <1991May1.121058.20933@osceola.cs.ucf.edu>
Sender: news@cs.mu.oz.au
Lines: 25

ssd@engr.ucf.edu (Steven S. Dick) writes:

>I've written my own write replacement [which I probably should release
>to the net] that lets you type your whole message before it sends it.

You don't need to write a "write" replacement to do that, you just
do

	write user <<!
	message
	!

	or

	cat | write user

but while that's sometimes useful it's not what write is meant for, you're
not supposed to sit and wait for the rest of the message after you see the
line with the sender's name on it - you're supposed to write back, write
is basically intended for interactive conversations, if your write makes
you finish the whole thing before the recipient gets to see any of it,
how can you possibly respond to his thoughts if your write has already
completed?

kre