ken@rochester.ARPA (SKY) (11/11/86)
In article <5357@brl-smoke.ARPA> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes: |[On filtering classes of messages, and designating terminals to receive | messages] Yes indeed. 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 instead of local hacks to wall/mesg/biff, etc? Ken
roy@phri.UUCP (Roy Smith) (11/12/86)
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!"