Path: utzoo!attcan!uunet!lll-winken!ames!pasteur!ucbvax!tolerant.UUCP!uucp
From: uucp@tolerant.UUCP (UNIX-UNIX Cp)
Newsgroups: comp.unix.microport
Subject: Submission for comp-unix-microport
Message-ID: <8901070908.AA06820@handel.TOLERANT>
Date: 7 Jan 89 09:08:05 GMT
Sender: uuclerk@ucbvax.BERKELEY.EDU
Lines: 18

Path: tolerant!voder!apple!claris!ames!amdcad!sun!pitstop!sundc!seismo!uunet!uport!ken
From: ken@uport.UUCP (Ken Chapin)
Newsgroups: comp.unix.microport
Subject: Re: Ramdisk usage on V/386
Keywords: ramd configuration
Message-ID: <288@uport.UUCP>
Date: 5 Jan 89 15:23:40 GMT
References: <176@wa3wbu.UUCP> <6515@killer.DALLAS.TX.US> <144@inxsvcs.UUCP>
Reply-To: ken@uport.UUCP (Ken Chapin)
Organization: Microport Systems, Scotts Valley, CA
Lines: 6

In article <144@inxsvcs.UUCP> mwg@inxsvcs.UUCP (Phil Blecker) writes:
>I took ramd out of /etc/atconf/systems/system.std without any problems. There
>appears to be a way to change the size of the "disk", but I don't want one

By changing a few things in the space.c of modules/ramd, the ram disk can be 
configurable.