[Info-vax] How do I make zip, unzip etc. available to all users?

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Thu Jan 7 03:41:20 EST 2016


Den 2016-01-07 kl. 07:04, skrev Phillip Helbig (undress to reply):
> In article <39e4ca88-0ee9-446b-b975-d405570bbcbd at googlegroups.com>,
> abrsvc <dansabrservices at yahoo.com> writes:
>
>> I have to agree with Phil here.  I too try to keep the system disk
>> "clean" from any non-DEC stuff.  I also use concealed devices so that I
>> am not tied to a particular device.  Since the "disk" is created during
>> startup so is available quite early.
>
> Related to this, refer to a disk by its physical name only once.  After
> that, use logical names.  The DISK$FOO created at MOUNT might be enough.
> With the logical name, it doesn't matter if it is a real disk, concealed
> device, shadow set, etc.
>

The "issue" with non-concealed logical names/disks, is whenever it is
used, the real physical disk namn is displayed. If you do a :

$ dir/nohead/notrail/out=somefile logical:[dir]*.*

to get a file for later processing of the files, you will get file
specifications with physical disk names, not the logical in the command.

This is particular an issue inthe case with Rdb, where where Rdb
stores the physical disk names in the database root file even if
you use logical names in your commands. The solution is to use rooted
and concealed logical names, they get stored as-is in Rdb and makes
it much easier to make changes in the physical storage system.

As a workaround, until you are able to "fix" the Rdb database, you end
up with defines like:

$ define/sys DKA100 DSA10:

Or whatever the old and new disk names was. And remember not to put
the ":" on the first one... :-)






More information about the Info-vax mailing list