Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!rpi!pawl!shadow From: shadow@pawl.rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga.tech Subject: Re: another 1.4 wish Message-ID: Date: 23 Aug 89 19:39:52 GMT References: <13227@well.UUCP> <525@tardis.Tymnet.COM> <1364@jolnet.ORPK.IL.US> Sender: usenet@rpi.edu Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 29 In-reply-to: swan@jolnet.ORPK.IL.US's message of 22 Aug 89 01:48:15 GMT On 22 Aug 89 01:48:15 GMT, swan@jolnet.ORPK.IL.US (Joel Swan) said: Joel> BTW- I have a hard time finding a spot in my startup-sequence to Joel> relabel RAM. It seems if I do it too early in my SS, I get an Joel> error code. I also must do it a few commands ahead of my loadwb Joel> if I remember right. I think it would give me validation errors Joel> or something. What I do is start my startup-sequence by installing ConMan and starting an AShell and killing the original CLI, but then the AShell mounts RAD:, and attempts to "relabel rad: vd0"... if it gets an error on either the mount or relabel, it runs RemRAD, prints an error, and does a "relabel ram: vd0" instead. Subsequent references are all to vd0:, copying files and assigning devices, etc. This way, it will use RAD: if it can, (and won't copy files it doesn't need to) and fall back on RAM: if RAD: fails. I no longer use the ASDG vdisk, but I was used to "VD0:" so I used it for the volume label of the main ramdisk. A "relabel ram: ram" precedes the "mount rad:" so if RAD: works, RAM: will have volume label ram:. *I* like it. :-) Deven -- Deven T. Corzine Internet: deven@rpi.edu, shadow@pawl.rpi.edu Snail: 2214 12th Street, Troy, NY 12180 Phone: (518) 271-0750 Bitnet: deven@rpitsmts, userfxb6@rpitsmts UUCP: uunet!rpi!deven Simple things should be simple and complex things should be possible.