Re: For the AdaOS folks

["Randy Brukardt" <randy@rrsoftware.com>]

"Warren W. Gay VE3WWG" <ve3wwg@NoSpam.cogeco.ca> wrote in message
news:z7iCd.15318$Y_4.1372013@read2.cgocable.net...
> > But in our hypothetical OS each possible way of access will be
represented
> > by some safe system object. These objects, when properly designed will
> > provide necessary administrative services.
>
> If you are a night watchman for a Mall, which situation makes it
> easier to sleep at night when you've locked up and gone home?
>
>    1. A mall with one or two doors on the outside to be
>       locked and checked.
>    2. A mall with thousands of doors on the outside to be
>       locked and checked.
>
> The answer is obvious. Sure, it is ok for other doors to exist
> inside the mall (for each store), which can be locked, but it
> only makes sense to choke the security at a minimal number
> of points.

There are other requirements than security! I think the fire dept. would be
pretty unhappy with (1) - at least if you ever let anybody in. Same holds
for OSes; you're going to need multiple ways to get things done; you can try
to minimize the number of "doors", but its unlikely that you can get down to
just one.

BTW, I think Dmitry's grand vision is on the right track. The tough part (as
always) is mapping that to something that still is practical. Why shouldn't
an Ada OS take advantage of Ada's features to provide persistence,
synchronization, and the like? Sure, you'll have to go beyond that, too, but
why not start with Ada's fine features in this area?

                      Randy.