Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!alberta!calgary!thompson
From: thompson@calgary.UUCP
Newsgroups: comp.sys.apollo
Subject: Re: AEGIS Vs UNIX
Message-ID: <947@vaxb.calgary.UUCP>
Date: Thu, 4-Jun-87 16:09:26 EDT
Article-I.D.: vaxb.947
Posted: Thu Jun  4 16:09:26 1987
Date-Received: Sat, 6-Jun-87 10:13:05 EDT
References: <870603192007.915098@HI-MULTICS.ARPA> <941@vaxb.calgary.UUCP>
Organization: U. of Calgary, Calgary, Ab.
Lines: 35
Summary: Some additional comments which are relevant but were missed in the prev. article.



Dan and I came up with a number of the comments which he posted. After he
posted it, we came up with a few others:

====================
        PRO
====================

The protected subsystem idea is both powerful and convienent. The ease with
which a group of programs and files can be isolated and controlled using the
protected subsystem tools is impressive

====================
        CON
====================

It is not apparently possible, without borrowing the entire display, to
obtain information regarding the user's activities (i.e. mouse movement,
button and key events, etc.) outside of the windows associated with a
process.

There appears to be no way to add system global error codes which will be
recognized by the error_$ system calls, or 'stcode'. While this is not really
a problem on UNIX systems, the ability to have defined codes for errors
occuring in site created systems would promote consistancy with the provided
error reporting characteristics of the system.

{ insert silly comment/standard disclaimer (there's a difference?) here }

-- 
-------------------------------------------------------
Bruce Thompson
University of Calgary , Computer Science Department
	(403)220-3538 (office)