> But that won't help if the /home/myname directory is not crossable for other users.

But it will. Permissions on user directories make no difference in this case - /etc/bash.bashrc is the system-wide initialization file for Bash; the only times it isn't read is if the shell is a login shell or the '--norc' or '--rcfile other_init_file' options are specified.

I do agree that this may be a case of the XY problem, though. It sounds like using a 10-ton hydraulic press to smash a fly - since modifying system-wide init files should be reserved for absolute emergencies and treated with utmost care.


--
"Language shapes the way we think, and determines what we can think about."
-- B. L. Whorf

In reply to Re^5: Bash Shell & Perl Library Path by oko1
in thread Bash Shell & Perl Library Path by Anonymous Monk

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.