From owner-freebsd-current Sun Apr 9 22:09:50 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA00955 for current-outgoing; Sun, 9 Apr 1995 22:09:50 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA00949 for ; Sun, 9 Apr 1995 22:09:48 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.8/8.6.6) id WAA20667; Sun, 9 Apr 1995 22:08:57 -0700 From: "Rodney W. Grimes" Message-Id: <199504100508.WAA20667@gndrsh.aac.dev.com> Subject: Re: talk - mesg y only To: mmead@goof.com (matthew c. mead) Date: Sun, 9 Apr 1995 22:08:57 -0700 (PDT) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org In-Reply-To: <199504100422.AAA02593@goof.com> from "matthew c. mead" at Apr 10, 95 00:22:34 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 864 Sender: current-owner@FreeBSD.org Precedence: bulk > > On Sun, April 9, 1995 at 09:29:12 (+0200), J. Wunsch wrote: > > > > Why does talk want mesg y all the time? > > > Ensure privacy for people who wish it. If nobody can write(1) you > > anything, why should they be able to bother you with talks? > > No - I mean why does talk require me to have my messages on to > INITIATE a talk with someone else. It shouldn't! :-0 I think it should, so that if the person you are trying to talk to either a) doesnt want to talk to you and can quick do a ``write bugger off, I'm busy :-)'' or b) talk back to you later after he comes back from a coffee break. It's not polite to initiate a talk session from a proc that does not have messages enabled. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD