Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!mintaka!olivea!apple!netcom!jbreeden
From: jbreeden@netcom.UUCP (John Breeden)
Newsgroups: comp.sys.novell
Subject: Re: Novell Certfication (hardware)
Message-ID: <20591@netcom.UUCP>
Date: 11 Jan 91 07:30:03 GMT
References: <1991Jan9.112347.37512@eagle.wesleyan.edu> <1991Jan10.183900.22664@world.std.com>
Organization: Netcom- The Bay Area's Public Access Unix System {408 241-9760 guest}
Lines: 21

In article <1991Jan10.183900.22664@world.std.com> jamesp@world.std.com (james M peterson) writes:
>Well----Novell certified hardware means that it runs netware w/o anything
>really weird happening.  does it run it well? Maybe.
>
>weird things.  I.E. "We guarantee that computer X is 100% compatable
>with netware versions a,b,c (and VAP..NLM...).  If customer finds this 

Now if a VAP or NLM can bomb a server (the 'ol ring 0 thing), how can any
hardware vendor (or even Novell) CERTIFY that each and every possible 
COMBINATION of MULTIPLE VAPs and NLMs won't do "weird" things. 

Seems pretty streight forward to say "vendor X's NLM" works fine but it gets
a little more complicated when it's "vendor X & Y's" or "X, Y & Z's" etc.

-- 
 John Robert Breeden, 
 netcom!jbreeden@apple.com, apple!netcom!jbreeden, ATTMAIL:!jbreeden
 -------------------------------------------------------------------
 "The nice thing about standards is that you have so many to choose 
  from. If you don't like any of them, you just wait for next year's 
  model."