I know it has saved me from accidentally making a directory in the wrong place. If I am not in $HOME, and run mkdir scripts/shell, as opposed to mkdir ~/scripts/shell, I would prefer the double check and failure when it notices scripts/ does not exist. Similarly: mkdir scrpts/shell, mkdir /ect/httpd/conf.... On Thu, Nov 29, 2018 at 3:25 PM rhubarbpieguy <rhubarbpieguy at gmail.com> 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 > -- Jeff Chapin President, CedarLug, retired President, UNIPC, "I'll get around to it" President, UNI Scuba Club Senator, NISG, retired -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20181129/c2ee2163/attachment.html>