Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!csd4.milw.wisc.edu!bbn!mailrus!caen.engin.umich.edu!conliffe
From: conliffe@caen.engin.umich.edu (Darryl C. Conliffe)
Newsgroups: comp.sys.apollo
Subject: Re: Processes in GPR_$borrow mode.
Summary: NO NO NO!
Message-ID: <43d0609a.b11a@falcon.engin.umich.edu>
Date: 13 Jun 89 04:00:00 GMT
References: <8906120536.AA14404@umix.cc.umich.edu>
Organization: U of M Engineering, Ann Arbor, Mich.
Lines: 32

In article <8906120536.AA14404@umix.cc.umich.edu>, GBOPOLY1@NUSVM.BITNET (fclim) writes:
> Hi,
[ comments about desire to interrupt borrow mode ]
> What I had in mind is that of vanilla Unix.  When a user logs in, the
> terminal is his.  Init (or is it getty) will do a
>       chown /dev/ttynn userid
> The user may wish to ignore all messages via
>       % mesg n
> which in effect does a
>       chmod 600 /dev/ttynn
> However, because root overrides all permission modes, when root issue
> a write(1) or wall(1), the message will still get thro.
> 
> How about putting some of the vanilla back into the DM/GPR ?
> 
> "Kludge, megakludges to the max!"
>                        --- Sonarman First Class, Ronald 'Jonesy' Jones.
> 
> fclim          --- gbopoly1 % nusvm.bitnet @ cunyvm.cuny.edu
> computer centre
> singapore polytechnic
> dover road
> singapore 0513.

NO NO NO!  Please don't forget that some people DO use borrow mode
for a reason, and undesired information appearing at unexpected times on
a workstation screen can ruin work, too!

Why not just ask vendors to avoid borrow mode when possible?  Applications
need not use it to cover the screen, and yet they will be well behaved.

Besides, I like my vanilla in vanilla wafers, *NOT* my workstation! ;=)