Date: Mon, 10 Apr 1995 10:57:28 -0400 From: "matthew c. mead" <mmead@goof.com> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: mmead@goof.com (matthew c. mead), joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.org Subject: Re: talk - mesg y only Message-ID: <199504101457.KAA01071@goof.com> In-Reply-To: Your message of Sun, April 9, 1995 22:08:57 -0700 References: <199504100422.AAA02593@goof.com> <199504100508.WAA20667@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, April 9, 1995 at 22:08:57 (-0700), Rodney W. Grimes wrote:
> > 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.
That's a reason that makes perfect sense to me. I'm going to
modify my talk so that it doesn't require this, however, because I tend to
like to talk people from a mesg n terminal (so I don't get interrupted if
someone else writes or talks me) and have one terminal I'm logged in from
mesg y (the terminal I want to get messages on).
-matt
--
Matthew C. Mead -> Virginia Tech Center for Transportation Research -
-> Multiple Platform System and Network Administration
Work Related -> mmead@ctr.vt.edu | mmead@goof.com <- All Other
---- ------- WWW -> http://www.goof.com/~mmead --- -----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504101457.KAA01071>