From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,85034d1ac78a66eb
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2002-03-26 12:23:50 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!nntp.abs.net!newsfeed.cwix.com!news.binc.net!kilgallen
From: Kilgallen@SpamCop.net (Larry Kilgallen)
Newsgroups: comp.lang.ada
Subject: Re: Ada Operating System
Date: 26 Mar 2002 14:23:45 -0600
Organization: Berbee Information Networks Corporation
Message-ID: <jaQf1fYhdsKD@eisner.encompasserve.org>
References: <a62kmf$giv$1@nh.pace.co.uk>
 <o2td8ug1chantij2e6j80kk56mrafp6e78@4ax.com> <a6825a$75c$1@nh.pace.co.uk>
 <3C88E0D1.89161C16@despammed.com> <a6m8h5$rpb$1@helle.btinternet.com>
 <a6nld6$i4n$1@nh.pace.co.uk> <jgo59u49ro74pbfvoek6ruqqa5o790mq90@4ax.com>
 <wcc8z8se0oe.fsf@shell01.TheWorld.com>
 <v30a9usnp895obfnu6ef8t9h6nnn9fkp1r@4ax.com> <3C9514DD.9CF1F84A@san.rr.com>
 <99da9u0909rsblfdcc1ru7jd2r9q461qhk@4ax.com>
 <a76lbh$8i42@news.cis.okstate.edu>
 <436o9uc7jg590rv5rb1l9v6be8vk49s278@4ax.com> <a7ntns$7hh$Organization: LJK
 Software
NNTP-Posting-Host: eisner.encompasserve.org
X-Trace: grandcanyon.binc.net 1017174229 18752 192.135.80.34 (26 Mar 2002
 20:23:49 GMT)
X-Complaints-To: abuse@binc.net
NNTP-Posting-Date: Tue, 26 Mar 2002 20:23:49 +0000 (UTC)
Xref: archiver1.google.com comp.lang.ada:21697
Date: 2002-03-26T14:23:45-06:00
List-Id: <comp.lang.ada>

In article <a7ntns$7hh$1@nh.pace.co.uk>, "Marin David Condic" <dont.bother.mcondic.auntie.spam@[acm.org> writes:
> What about an OS that deliberately let you set up Foot Shooting Mode?
> Suppose it was ultra-secure in "Normal" processing, but if the Administrator
> were to boot it up with some secret-handshake, etc., it enabled a process to
> run with all capabilities? Your process could switch to Supervisor mode,
> read & write directly to physical memory & devices, etc? When you need a
> safe OS - it runs safe. When the OS gets in your way, move it aside. That
> might make for a distinct product that would satisfy a whole class of needs.

I don't see why a special boot mode is required, compared to just
letting people have privileges (or not).

Today I can audit whether users log into their privileged accounts,
using out-of-the-box capabilities.  I can even control it if I need
to, from an account whose only "privilege" is the ability to turn
on and off the privileged logins.

I don't see any reason to send an Ada Operating System scurrying
in a different direction thaan that which is traditional in multiuser
operating systems.