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

David Froble davef at tsoft-inc.com
Tue Jan 5 18:01:09 EST 2016


lists at openmailbox.org wrote:
> On Tue, 5 Jan 2016 12:25:54 -0500
> Stephen Hoffman via Info-vax <info-vax at rbnsn.com> wrote:
> 
>> On 2016-01-05 15:59:52 +0000, David Froble said:
>>
>>> lists at openmailbox.org wrote:
>>>> Hi,
>>> Not sure what you're asking, so the following may not be the answer 
>>> you're seeking ....
>>>
>>>> I downloaded copies of zip, unzip etc. from various freeware archives.
>>>> How do I make these and other executables available to all users?
>>
>> See the example command procedure available in 000TOOLS in any of the 
>> Freeware distros.   That references all of the tools stored in the 
>> 000TOOLS area.
> 
> Thanks, I will take a look at it.
> 
>>> $ SET PROTECTION=(W:RWED) ZIP.EXE
>>>
>>> The above allows anyone to READ, WRITE, EXECUTE, and DELETE the file.
>>>
>>> Or maybe:
>>>
>>> $ SET PROTECTION=(W:RWE)
>>
>> Generally use RE here (or an ACE that allows specific groups RE 
>> access), and generally not RWED nor RWE.
>>
>> Most folks should not be overwriting nor deleting these or other shared
>> tools.
> 
> Thanks. Do you have to be able to read it to make it executable? If not,
> why both RE?
> 
>>>> Where should these kinds of programs be placed in the system and how
>>>> do I modify whatever logon proc(s) to allow them to be used?
> 
> I see you guys are all dodging this question. Hmm, I wonder what that
> means...
> 
>>> It really doesn't matter where they are, as long as users can access 
>>> the files.   This might require changing the protection masks for the 
>>> directories where the executable is located.
>>>
>>> In SYS$MANAGER:SYLOGIN.COM you could have something such as:
>>>
>>> $ ZIP :== $[location]ZIP
>>>
>>> The above supposes that all users automatically invoke the SYLOGIN 
>>> procedure upon logging in.
>>
>> Ayup.    OP can install the GNV kit, and reference the copies of these 
>> and other tools in that kit, too.
> 
> What's GNV? Sounds suspiciously like Gnu's not VMS! If so, no thanks...no
> gnu anything on this system. If I wanted crapware I could stay on Linux.
> 

Many people here know what an opinionated bigot I am, so beware.

I strong disapprove of placing anything in the VMS OS directories.  If you have 
something else, use another location, or, create a location for such.  Stay out 
of the OS directories, they aren't yours ....

That written, I got two sharable RTL executables in SYS$SHARE:.  Go figure ...



More information about the Info-vax mailing list