<html dir="ltr"><head></head><body style="text-align:left; direction:ltr;"><div>When using mkdir in a script, mkdir gives you the option of checking the status code returned to validate your command is doing what you intended, where you intended, or blindly assuming you really know where $PWD is running that script.</div><div><br></div><div>Put that script in your $PATH and interesting results may result depending on where $PWD is when executing that script and how you reference the path you are trying to create.</div><div><br></div><div>On Thu, 2018-11-29 at 09:25 -0600, rhubarbpieguy wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><pre>The mkdir command requires the -p switch if creating a child directory </pre><pre>with a non-existing parent. For instance, 'mkdir /parent/child' will </pre><pre>not work if /parent doesn't exist.</pre><pre><br></pre><pre>I'm not losing sleep over this and I doubt things will change, but it </pre><pre>seems the -p action should be the default? Is there a scenario when one </pre><pre>wouldn't want to create the parent when creating the child?</pre><pre><br></pre><pre><br></pre><pre>_______________________________________________</pre><pre>TCLUG Mailing List - Minneapolis/St. Paul, Minnesota</pre><pre><a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a></pre><pre><a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a></pre><pre><br></pre></blockquote></body></html>