That's a bad idea.

You shouldn't change the permissions on files in /usr directories except for the ones that you (the system administrator) own like in /usr/local.

Furthermore, running a command like chmod -R is especially dangerous, if you do not understand what you are doing.

The *.pm files in /usr are supposed to have 0644 permissions. They should not be set with execute. They are not executable files, after all.

Having said all that, this particular change is most likely benign. But you should never change files in the /usr directory except your own. These files and their permissions are managed by the system and rpm(8) in the OP's case.

Run the command rpm -V perl to see all the "damage" now.

In reply to Re^2: perl lost its modules! by garry
in thread perl lost its modules! by seandarcy

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.