On 25/06/2016 05:07, Ken Moffat wrote:
> At the moment, there is a problem with file permissions in texlive
> texmf for 2016 (like the redundant files included in the source, it
> will get fixed one day), so for the moment I'm trying to fix these
> up after the install.
>
> On my previous build I eventually realised I was not addressing the
> two files with 700 perms, but I was shocked to see that I had only
> managed to fix the few files with 640 perms, not the vast number
> with 600 perms. At that time I thought I had maybe not saved the
> updated script before I ran the build, so I added the 700 test and
> saved it.
>
> But now it looks as if only the *last* of alternatives is being
> used. And yet find itself is finding all of them
>
> What I have at hte moment is (one line, although it will wrap here):
>
> find /opt/texlive/${TEXYEAR}/texmf-dist -type f -perm 600 -o -perm
> 640 -o -perm 700 -exec chmod -v 644 {} \;
>
> From the two runs I can see that there are 667 files with 600 perms,
> 5 with 640, and 2 with 700.
>
> After the second run I tried:
>
> find /opt/texlive/2016/texmf-dist/ -type f -perm 600 -o -perm 640 -o
> -perm 700 | wc -l
> 672
I think you need parentheses (of course xargs is good too!). As usual in
computer languages, 'or' has less precedence than 'and', and in "find" syntax,
'and' is implied if 'or' (ie -o) is not given... You could achieve what you
need with:
find /opt/texlive/${TEXYEAR}/texmf-dist -type f \( -perm 600 -o -perm
640 -o -perm 700 \) -exec chmod -v 644 {} \;
(parentheses need to be escaped for the shell).
Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
