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. 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. On Thu, 2018-11-29 at 09:25 -0600, rhubarbpieguy wrote: > The mkdir command requires the -p switch if creating a child directory > with a non-existing parent. For instance, 'mkdir /parent/child' will > not work if /parent doesn't exist. > > I'm not losing sleep over this and I doubt things will change, but it > seems the -p action should be the default? Is there a scenario when one > wouldn't want to create the parent when creating the child? > > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20181129/a72382f7/attachment.html>