Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 alpha 4/15/85; site ucbvax.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!ucbvax!info-vax
From: info-vax@ucbvax.ARPA
Newsgroups: fa.info-vax
Subject: Re: Allocating your own terminal
Message-ID: <7898@ucbvax.ARPA>
Date: Fri, 7-Jun-85 00:28:02 EDT
Article-I.D.: ucbvax.7898
Posted: Fri Jun  7 00:28:02 1985
Date-Received: Sat, 8-Jun-85 01:25:50 EDT
Sender: daemon@ucbvax.ARPA
Organization: University of California at Berkeley
Lines: 23

From: Richard Garland <OC.GARLAND@CU20B.ARPA>

Allocating terminals:

We have several lines that have special devices on them, i.e. an Evans and
Sutherland PS300.  These are not (usually) used for logins so I set them 
either

	SET DEV/PROT=(S:RWLP,O:RWLP,G:RWLP,W)/OWN=(xxx,0)   ttxy:

		or
	..........                       W:RWLP) ....

The former for lines belong to a certain group and excluding the world,
the later for line available to the world.  Typically a user logs onto another
terminal and these become output devices.

Another approach my be to give the third party software some privilege
to allocate the line (i.e. INSTALL it).   This would require that you
trust the software to not anything wierd with enhanced privilege.

					Rg
-------