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 12:41:16 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!paloalto-snf1.gtei.net!chcgil2-snh1.gtei.net!chcgil2-snf1.gtei.net!news.gtei.net!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: Ada OS Kernel features Date: 6 Sep 2001 14:41:10 -0500 Organization: LJK Software Message-ID: 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> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 999805271 6888 192.135.80.34 (6 Sep 2001 19:41:11 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Thu, 6 Sep 2001 19:41:11 +0000 (UTC) Xref: archiver1.google.com comp.lang.ada:12838 Date: 2001-09-06T14:41:10-05:00 List-Id: 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.