kim@amdahl.uts.amdahl.com (Kim DeVaughn) (11/16/88)
[ "A car is just a big purse on wheels." --Johanna Reynolds ]
Getting 1.3 up and running with all my various "stuff" (FaccII, DMouse,
vd0:, rad:, clock, shell(s), etc.) has been an interesting and funfilled
time :-) ...
But it has reminded me of a problem that I've always seen with ASDG's
RRD (vd0:), that's really quite annoying, and one that I really don't
understand since it's so counter-intuitive.
The RRD is usually very good about recovering for me ... except when I
do several Cntl-Amiga-Amiga reboots intentionally spaced fairly close
together (to check on the latest changes made to my startup-sequence).
You know, alter the s-s, reboot to see how it works, alter the s-s again,
reboot ... etc.
I can usually go thru 2 or maybe 3 such cycles, and the RRD will recover,
but on the next one, I get my dreaded "copying sys:c to vd0:c ..." message
printed. The RRD failed to recover, and now it's time for coffee, etc.
None of the s-s alterations are the kind of things that would cause any
problems in themselves (changing echo'd msgs, etc.), so WHY is the RRD
so (seemingly) sensitive to several reboots almost in a row? Whereas,
if I *do* a bunch of stuff between the reboots (run a few applications,
and generally futz around a bit), the RRD has no problem in recovering.
Anyone else noticed this behavior? Any ideas? Eric?
/kim
--
UUCP: kim@amdahl.amdahl.com
or: {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
DDD: 408-746-8462
USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086
BIX: kdevaughn GEnie: K.DEVAUGHN CIS: 76535,25