The -m argument to the (presumably) GNU mkdir command makes it set the permissions disregarding the process' umask. The Perl mkdir call is just calling the bare mkdir(2) system call which honours the umask. If you don't want the umask to affect things either explicitly set it to a known value or call chmod yourself after making the directory.

Update: And with strace you can see the later is exactly what the GNU mkdir is doing underneath the hood: 

$ strace -e chmod,mkdir mkdir -m0777 spoo
mkdir("spoo", 0777)                     = 0
chmod("spoo", 0777)                     = 0

[download]

In reply to Re: Why does unix mkdir and perl mkdir behave differently? by Fletch
in thread Why does unix mkdir and perl mkdir behave differently? by tphyahoo

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.