Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ames!ucbcad!ucbvax!jade!eris!mwm
From: mwm@eris.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: RRD filling
Message-ID: <3108@jade.BERKELEY.EDU>
Date: Thu, 9-Apr-87 19:55:01 EST
Article-I.D.: jade.3108
Posted: Thu Apr  9 19:55:01 1987
Date-Received: Sat, 11-Apr-87 15:12:04 EST
References: <8704092011.AA20151@cory.Berkeley.EDU>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: mwm@eris.BERKELEY.EDU (Mike (My watch has windows) Meyer)
Organization: Missionaria Phonibalonica
Lines: 30

>>I also wanted more in my RRD than would fit on one disk.  My solution was
>>to put a line in my startup sequence (copy wb2: to vd0: all) to get the
>>rest of the stuff.  It even reminds me to put in volume wb2 in case I
>>forget.  Could this save you from doing a reboot?

I took a different route, being a believer in modules. I've got a set
of scripts in s: named "make-<package>-vd". They all do the same kinds
of things: copy stuff to vd0: if it's not there, and then make the
assigns that package wants. It copies from the volume name that the
package lives on, so it also asks for them if I forget.

An alternative strategy I've considered is to have a file called
"make" on each disk that does the same thing. That way, "execute
df1:make" will do the trick.

While playing with TeX, I had close to 2meg in vd0:. When I start
playing with LaTeX, I expect things to go over 2Meg in vd0:.

As an aside, I'm using Katin's (sp?) vdk: driver instead of the ASDG
rrd driver (which is why ASDG hasn't got my $10). It allows me
multiple devices, but doesn't need it, as the same mountlist entry
works both with and without expansion ram. It also doesn't have a
fixed size limit.

	<mike
--
Here's a song about absolutely nothing.			Mike Meyer        
It's not about me, not about anyone else,		ucbvax!mwm        
Not about love, not about being young.			mwm@berkeley.edu  
Not about anything else, either.			mwm@ucbjade.BITNET