Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: comp.unix.questions
Subject: Re: Unsolicited messages (was Re: Slaying Gould dragon...)
Message-ID: <2494@phri.UUCP>
Date: Tue, 11-Nov-86 20:05:27 EST
Article-I.D.: phri.2494
Posted: Tue Nov 11 20:05:27 1986
Date-Received: Wed, 12-Nov-86 10:09:47 EST
References: <1307@ttrdc.UUCP> <5357@brl-smoke.ARPA> <22332@rochester.ARPA>
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 21

In article <22332@rochester.ARPA> ken@rochester.UUCP (SKY) writes:
> I would like, for example, to designate one window for messages when
> I'm on a Sun.  We have the biff service, why not a mesg service?
> Has anybody worked on a general solution [...]

	On my Sun-3, running 3.0, all the usual write, biff, wall, etc
messages come up in my console window.  I havn't looked into it too
closely, but it seems like it works something like this:

	Programs all see that I'm logged in on /dev/console and write to me
there.  The console device driver is just an indirect driver (much like
/dev/tty) which hands off I/O to the apropriate pty.  Presumably when I
designate a window as a console, the shelltool issues some sort of ioctl to
indicate that the particular pty it is using is to be considered the
console from now on.  Works fine.  Seems pretty general.
-- 
Roy Smith, {allegra,cmcl2,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016

"you can't spell deoxyribonucleic without unix!"