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-Thread: 103376,37c1639cf6a3bbba X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!wns14feed!worldnet.att.net!204.71.34.3!newsfeed.cwix.com!news.binc.net!kilgallen From: Kilgallen@SpamCop.net (Larry Kilgallen) Newsgroups: comp.lang.ada Subject: Re: A scary story from the real world. Date: 9 Nov 2007 23:44:23 -0600 Organization: LJK Software Message-ID: <6dnoNdRLROF5@eisner.encompasserve.org> References: <0Q0Zi.409$CT3.318@newsfet01.ams> NNTP-Posting-Host: eisner.encompasserve.org X-Trace: grandcanyon.binc.net 1194673369 10176 192.135.80.34 (10 Nov 2007 05:42:49 GMT) X-Complaints-To: abuse@binc.net NNTP-Posting-Date: Sat, 10 Nov 2007 05:42:49 +0000 (UTC) Xref: g2news1.google.com comp.lang.ada:18247 Date: 2007-11-09T23:44:23-06:00 List-Id: In article , Brian May writes: > I see only two solutions: > > 1. Microsoft write or review drivers themselves. Unlikely to > happen. Even with an open source model like Linux, some drivers that > end up in the kernel are horrible (or so I have heard); there are > simply too many drivers to review and possibly rewrite every one. Some hardware vendors are unwilling to share the details of how their hardware works with other companies.