From: CSBVAX::CSBVAX::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 1-MAR-1989 20:36 To: MRGATE::"ARISIA::EVERHART" Subj: Patch to PHOTO.C to avoid requiring PHY_IO privilege Received: From KL.SRI.COM ([0.0.0.0]) by CRVAX.SRI.COM with TCP; Wed, 1 MAR 89 15:02:40 PDT Received: from gold.bacs.indiana.edu by KL.SRI.COM with TCP; Wed, 1 Mar 89 14:37:35 PST Date: 1 Mar 89 17:29:00 EST From: "IVAX::IJAH400" Subject: Patch to PHOTO.C to avoid requiring PHY_IO privilege To: "info-vax" [] I got a copy of PHOTO.C a while back that corrected a problem on 8800s. There was something about PHOTO that I was always curious about: We are running a patch here so we don't have to install it with PHY_IO privilege. The original code does a IO$_SETCHAR (which requires PHY_IO) in the routine fix_a_tw(). I was wondering why the *permanent* characteristics have to be set there. My patch consists of making tw_chn global, setting the *temporary* terminal characteristics of the TW device with an IO$_SETMODE (which doesn't require PHY_IO) in fix_a_tw(), then not deassigning the TW channel until immediately after the LIB$SPAWN call in low_lib_spawn(). This way there is always a channel open on the TW device (first me, then the spawned subprocess), so the temporary characteristics don't go away. This seems to work exactly as before except that it doesn't require PHY_IO. Does anyone know of anything this would break? - Jim Harvey, IUPUI Computing Services (Indiana University) Internet: ijah400%ivax.decnet@gold.bacs.indiana.edu BITNET: ijah400@indyvax []