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,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6394e5e171f847d1 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-09-06 15:38:02 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!212.74.64.35!colt.net!newspeer.clara.net!news.clara.net!news5-gui.server.ntli.net!ntli.net!news2-win.server.ntlworld.com.POSTED!not-for-mail From: "chris.danx" Newsgroups: comp.lang.ada References: <9n4euv$t9m$1@slb6.atl.mindspring.net> <3B964C7A.BC04374E@icn.siemens.de> <9n5o9n$37a$1@slb7.atl.mindspring.net> <3%ul7.3362$9z1.440040@news6-win.server.ntlworld.com> Subject: Re: Ada OS Kernel features X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Message-ID: Date: Thu, 6 Sep 2001 23:32:41 +0100 NNTP-Posting-Host: 62.253.12.114 X-Complaints-To: abuse@ntlworld.com X-Trace: news2-win.server.ntlworld.com 999815573 62.253.12.114 (Thu, 06 Sep 2001 23:32:53 BST) NNTP-Posting-Date: Thu, 06 Sep 2001 23:32:53 BST Organization: ntlworld News Service Xref: archiver1.google.com comp.lang.ada:12854 Date: 2001-09-06T23:32:41+01:00 List-Id: "Larry Kilgallen" wrote in message news:d8$8gnF$GFEk@eisner.encompasserve.org... > In article , "chris.danx" 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?