Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!mordor!sri-spam!rutgers!cmcl2!phri!roy
From: roy@phri.UUCP (Roy Smith)
Newsgroups: news.admin
Subject: Re: Forgeries: a suggestion for bringing them under control
Message-ID: <3129@phri.UUCP>
Date: 1 Feb 88 03:44:30 GMT
References: <1129@hao.ucar.edu> <1133@hao.ucar.edu> <784@brandx.rutgers.edu>
Reply-To: roy@phri.UUCP (Roy Smith)
Organization: Public Health Research Inst. (NY, NY)
Lines: 17

In article <784@brandx.rutgers.edu> webber@brandx.rutgers.edu (Webber) writes:
> if the playing of rogue were crashing the system, then it would clearly
> be something worth careful investigation.  After all, rogue isn't an
> isolated kernel call, but instead uses much the same calls as the rest of
> the system so if there was something wrong with it there would be other
> problems too.

	Interesting point.  Depends on your point of view.  If I were an SA
using system software under a software support contract and my version of
rogue caused a kernel crash, I would sure as hell expect the vendor to find
the problem, taking exactly the argument outlined above.  On the other
hand, until the problem got fixed, you bet your bippies I'd outlaw rogue on
the system.  It's nice to argue how things should be, but people still
gotta get their work done.
-- 
Roy Smith, {allegra,cmcl2,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016