From owner-freebsd-bugs Wed Sep 27 14:20:06 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA14955 for bugs-outgoing; Wed, 27 Sep 1995 14:20:06 -0700 Received: (from gnats@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id OAA14946 ; Wed, 27 Sep 1995 14:20:03 -0700 Date: Wed, 27 Sep 1995 14:20:03 -0700 Message-Id: <199509272120.OAA14946@freefall.freebsd.org> To: freebsd-bugs Cc: From: J Wunsch Subject: Re: bin/746: `talk' forbids talking from write-protected terminal for no good reason Reply-To: J Wunsch Sender: owner-bugs@FreeBSD.org Precedence: bulk The following reply was made to PR bin/746; it has been noted by GNATS. From: J Wunsch To: hohmuth@inf.tu-dresden.de Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/746: `talk' forbids talking from write-protected terminal for no good reason Date: Wed, 27 Sep 1995 22:09:09 +0100 (MET) As hohmuth@inf.tu-dresden.de wrote: > > The `talk' program has a misfeature in that it cannot be used except > from a terminal with messages on ("mesg y"). When used from a > write-protected terminal (messages off, "mesg n"), it complains that > ``The callee cannot write to this terminal, use "mesg y"''. This has been discussed before with the conclusion that this feature is believed to be okay. For example, the callee migh want to respond to the talk request with a short message via write(1) saying that he's going to have the talk later, instead of actually invoking the talk right now. Lest somebody else objects, i'm going to close this report within a couple of days. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ Never trust an operating system you don't have sources for. ;-)