Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ncoast.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!cwruecmp!atvax!ncoast!bsa
From: bsa@ncoast.UUCP (Brandon Allbery (the tame hacker on the North Coast))
Newsgroups: net.unix-wizards
Subject: Re: How do *you* debug device drivers?
Message-ID: <534@ncoast.UUCP>
Date: Mon, 7-Jan-85 18:05:01 EST
Article-I.D.: ncoast.534
Posted: Mon Jan  7 18:05:01 1985
Date-Received: Fri, 11-Jan-85 05:00:00 EST
References: <541@vu44.UUCP> <317@rlgvax.UUCP> <28@osu-eddie.UUCP>
Reply-To: bsa@ncoast.UUCP (Brandon Allbery (the tame hacker on the North Coast))
Organization: The North Coast Xenix System, Cleveland
Lines: 12
Summary: 

System V may be on its way to a solution.  It seems to me that someone
could write a 'fake kernel' to run as a Unix user process, and use that
to debug device drivers., provided that a user address space can be >256K.
(of course, 512K might also do, since it wouldn't have to be a full multiuser
kernel, just a device driver debugging aid).

--bsa
-- 
  Brandon Allbery @ decvax!cwruecmp!ncoast!bsa (..ncoast!tdi1!bsa business)
	6504 Chestnut Road, Independence, Ohio 44131   (216) 524-1416
    Who said you had to be (a) a poor programmer or (b) a security hazard
			     to be a hacker?