From owner-freebsd-bugs Thu Sep 28 09:41:13 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA19812 for bugs-outgoing; Thu, 28 Sep 1995 09:41:13 -0700 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA19807 for ; Thu, 28 Sep 1995 09:41:10 -0700 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id KAA20546; Thu, 28 Sep 1995 10:39:07 -0600 Date: Thu, 28 Sep 1995 10:39:07 -0600 From: Nate Williams Message-Id: <199509281639.KAA20546@rocky.sri.MT.net> To: hohmuth@inf.tu-dresden.de (Michael Hohmuth) Cc: freebsd-bugs@freefall.freebsd.org Subject: Re: bin/746: `talk' forbids talking from write-protected terminal for no good reason In-Reply-To: <199509281400.HAA14705@freefall.freebsd.org> References: <199509281400.HAA14705@freefall.freebsd.org> Sender: owner-bugs@FreeBSD.org Precedence: bulk Michael Hohmuth writes: [ Talk not working unless the user's terminal has write priv's ] > I believe this is an issue of the user's policy, not of the system's. > I don't understand why a program should intentionally be crippled in > order to enforce a policy the user may not want. If the user want's to change it, they have access to the source. :) I hate to sound obnoxious, but the issue has already been discussed at length, and I agree that the current behavior is the best. The behavior also keeps folks from bothering other people be constantly starting talk sessions and then breaking them off, making the callee unable to respond. Nate