From owner-freebsd-current  Wed Jul  5 18:33:27 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA15473
          for current-outgoing; Wed, 5 Jul 1995 18:33:27 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id SAA15466
          for <current@freebsd.org>; Wed, 5 Jul 1995 18:33:19 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id LAA21203; Thu, 6 Jul 1995 11:28:28 +1000
Date: Thu, 6 Jul 1995 11:28:28 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199507060128.LAA21203@godzilla.zeta.org.au>
To: hohmuth@inf.tu-dresden.de
Subject: Re: bin/594: "mkdir -p some/path/" fails to create last path component when path has trailing slash
Cc: current@freebsd.org
Sender: current-owner@freebsd.org
Precedence: bulk

>	"mkdir -p some/path/" fails to create last path component when
>	path has trailing slash

Note that ordinary mkdir(1) and mkdir(2) also fail to create "foo/"
although POSIX specifies that paths to directories may have an optional
trailing slash.  I had this fixed in 1.1.5.  There is an old PR about it.

mkdir -p "foo/" has the additional bug that it exits with status 0 after
failing to create "foo/".

Bruce