aegnor@bsu-cs.bsu.edu (David C. Powell) (09/24/89)
I have another suggestion for 1.4, I have started using RAD: and VD0: extensively, and have found *1* thing I MISS using RAD: as opposed to a 'true' disk. The ability to 'write protect' the RAD: and/or the VD0: could this possibly be added via an INFO select in 1.4? I still use Transformer, and with RAD: in place, it survives, but SOME of its files get 'overwritten' making it have R/W errors. I know Transformer would probably still do this, but other things (VIRI) would have a semi-hard time (IMHO) if they 'see' the RAD: as being READ-ONLY. Am I off base? Is this impossible? *I* do not know, anybody from CA wanna comment on this? Thanks! David C. Powell M.I.S. Senior Ball State University Muncie, Indiana *-David Powell :ARPA: aegnor@bsu-cs.bsu.edu--------------------------* | \/ President :UUCP: <backbones>!{iuvax,pur-ee}!bsu-cs!aegnor | | /\etwnk Industries, Ltd. : | *-"If it doesn't work, we DIDN'T do it!"-----------------------------*
ccplumb@rose.waterloo.edu (Colin Plumb) (09/26/89)
In article <10156@bsu-cs.bsu.edu> aegnor@bsu-cs.bsu.edu (David C. Powell) writes: >The ability to 'write protect' the RAD: and/or the VD0: >could this possibly be added via an INFO select in 1.4? I still use >Transformer, and with RAD: in place, it survives, but SOME of its files >get 'overwritten' making it have R/W errors. I know Transformer would >probably still do this, but other things (VIRI) would have a semi-hard >time (IMHO) if they 'see' the RAD: as being READ-ONLY. There already is such a command in 1.3. CLI-only, at the moment. You supply a passkey (a 32-bit number) and must supply the same one to unlock the volume. I do not believe the protection survives reboots. Note that a 1.3-aware virus could extract the key from the system, and anything could hit the trackdisk.device directly. I forget the name (I don't have my 1.3 manual handy), but I've implemented it... -- -Colin