Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 Mar 2001 14:41:53 -0800
From:      Kent Stewart <kstewart@urx.com>
To:        Alfred Perlstein <bright@wintelcom.net>
Cc:        Dennis <dennis@etinc.com>, hackers@FreeBSD.ORG
Subject:   Re: if_fxp - the real point
Message-ID:  <3AAFF3B1.A4C759D8@urx.com>
References:  <20010314090915.D29888@fw.wintelcom.net> <200103092332.f29NW4785782@gollum.esys.ca> <20010309221250.2384337B71B@hub.freebsd.org> <200103092332.f29NW4785782@gollum.esys.ca> <20010314123503.C74704@daemon.ninth-circle.org> <5.0.0.25.0.20010314110743.02373a00@mail.etinc.com> <20010314090915.D29888@fw.wintelcom.net> <20010314104748.A31046@dragon.nuxi.com> <5.0.0.25.0.20010314165014.03dcb7b0@mail.etinc.com> <20010314134314.M29888@fw.wintelcom.net>

next in thread | previous in thread | raw e-mail | index | archive | help


Alfred Perlstein wrote:
> 
> * Dennis <dennis@etinc.com> [010314 13:36] wrote:
> > At 01:47 PM 03/14/2001, you wrote:
> > >On Wed, Mar 14, 2001 at 09:09:15AM -0800, Alfred Perlstein wrote:
> > > > how many times does windows crash because of poorly written drivers
> > > > rather than flaws in the core OS? (*)
> > >
> > >ALL the time.  Microsoft has given the UC-Davis security and formal
> > >verification lab a multi-year grant to look at this problem.
> > >(the approach being researched is "model checking")
> >
> > Why would they need to do that? Every time you load a program it updates
> > the libraries, breaking older programs. Its a philosophical problem. You
> > dont need a grant to figure it out.
> 
> I think the money is for the solution. :)

With 2000 and above, your system will check for non-digitally signed
dll's and etc. The rule is pretty well enforced but will let you
install around it. If you do, you may have shot yourself in the foot.
You can recover but you have to run sfc from a command prompt window.
That doesn't help you with the product built around the old dll's and
with the stupid install. You also really need to have the source entry
for the registry pointing to your HD. Otherwise, you are constantly
switch the install CD and the sp-1 CDs. The checking takes hours on
large systems but is massively longer if you have to spent the time
switching CD's.

I think Whistler is heading towards including dll's and etc. in the
install program's space. You can't read too much about it right now.
That gets around the problem with multiple copies because you can have
your own, which people assume you have tested your product against and
not affect a different product. That is very similar to the problem we
are seeing right now with getopt.h. Libgnugetopt installed a terrible
version of getopt.h into /usr/local/include. It wasn't a terrible
product to libgnugetopt but to anything else that pointed their header
includes to that directory. Then products such as KDE-2.1 come along
and try to use it. The KDE-2.1 build bombed because the else clause in
the old gnu getopt.h has no arguments defined for non-gnu libraries
and tight checking kills the compile.

Kent

> 
> --
> -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org]
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Kent Stewart
Richland, WA

mailto:kbstew99@hotmail.com
http://kstewart.urx.com/kstewart/index.html
FreeBSD News http://daily.daemonnews.org/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AAFF3B1.A4C759D8>