Re: Ada OS Kernel features

["chris.danx" <chris.danx@ntlworld.com>]

"Larry Kilgallen" <Kilgallen@SpamCop.net> wrote in message
news:d8$8gnF$GFEk@eisner.encompasserve.org...
> In article <UWOl7.11352$592.628767@news2-win.server.ntlworld.com>,
"chris.danx" <chris.danx@ntlworld.com> writes:
> >
> >> > I really don't get why a driver must have access to system structures
or
> >> > atleast those in kernel space, can you explain this?
> >>
> >> A driver has access to raw hardware.  Therefore it necessarily has
> >> access to the system -- it could rewrite the copy of the OS on disk
> >> if it chose.
> >
> > Perhaps, but that's a problem that could be solved, in part, by
restricting
> > what the drivers allowed to access.  Video drivers have no business
using
> > the disk, so their access to disk access ports should be denied.
Similar
> > schemes should be used when appropriate.  It should not be possible for
a
> > driver to access things willy nilly.
>
> My impression was that the goal was to use existing hardware that is
> widely available.

Yes. why? Do you think that won't work across all hardware?