From owner-freebsd-current Mon Apr 10 08:33:35 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id IAA00865 for current-outgoing; Mon, 10 Apr 1995 08:33:35 -0700 Received: from mercury.unt.edu (mercury.unt.edu [129.120.1.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id IAA00859 for ; Mon, 10 Apr 1995 08:33:33 -0700 Received: from gab.unt.edu by mercury.unt.edu with SMTP id AA05840 (5.65c/IDA-1.4.4 for ); Mon, 10 Apr 1995 10:33:30 -0500 Received: from GAB/MAILQUEUE by gab.unt.edu (Mercury 1.13); Mon, 10 Apr 95 10:33:30 CST6CDT Received: from MAILQUEUE by GAB (Mercury 1.13); Mon, 10 Apr 95 10:33:23 CST6CDT From: "John Booth" Organization: University of North Texas To: freebsd-current@freefall.cdrom.com Date: Mon, 10 Apr 1995 10:33:17 CST6CDT Subject: Re: talk - mesg y only Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: <597B99010D@gab.unt.edu> Sender: current-owner@FreeBSD.org Precedence: bulk > > > Why does talk want mesg y all the time? I liked the way 1.1.5 defaulted to mesg y. > > Ensure privacy for people who wish it. If nobody can write(1) you They could put mesg n in a preference file (.tcshrc .cshrc etc.) I remember first going to 2.0R and being confused as to why I couldn't write or talk anyone. Then it dawned mesg n was default. I started putting mesg y in any new accounts I created. (Didn't like having to su and change their tty to make it writeable!!!). ---------------------------------------------------------------------- College of Arts & Sciences Computing Services John A. Booth, john@gab.unt.edu