<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/23/2017 08:21 PM, Matt Zabojnik
wrote:<br>
</div>
<blockquote
cite="mid:CAEOKyjBGY6RsOV_XrNFs9PCm7Cs=D+ghSsh302SsSSS_=kQ9DQ@mail.gmail.com"
type="cite">
<p dir="ltr">Thank you. Where can I find more information for
workable perms?</p>
</blockquote>
<p><font face="FreeSerif">Evidently you're living under Windows, in
which case a UNIX/Linux sense of perms isn't part of your
filesystem. Thus, creating a *.zip from component files where
UNIX/Linux perms don't have meaning (and consequently are often
given zero values i.e. no access), the rest of us living in such
a world get stuck with Windows' blindly ignorant misadventures.
Surprise, surprise.<br>
</font></p>
<p><font face="FreeSerif">Bottom line summary is that UNIX/Linux
filesystem permissions reflect the trio owner/group/other, each
of which has in turn a trio of permission bits for read/write/execute,
such that owner normally has read/write access to files, group
and other are generally read-only, and directories also have
execute permission, where the concept of "execute" on a
directory actually means "searchable." In command shell
CLI-speak, "chmod -R u+rwX,go+rX mod*" was necessary to fix your
files' perms.<br>
</font></p>
</body>
</html>