From owner-freebsd-current  Sat Jul  8 00:47:15 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id AAA08970
          for current-outgoing; Sat, 8 Jul 1995 00:47:15 -0700
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA08744
          for <current@freebsd.org>; Sat, 8 Jul 1995 00:46:56 -0700
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD4.4)
	id RAA17990; Sat, 8 Jul 1995 17:45:45 +1000
From: michael butler <imb@scgt.oz.au>
Message-Id: <199507080745.RAA17990@asstdc.scgt.oz.au>
Subject: Re: bin/594: "mkdir -p some/path/" fails to create last path component when path has trailing slash
To: bde@zeta.org.au (Bruce Evans)
Date: Sat, 8 Jul 1995 17:45:43 +1000 (EST)
Cc: current@freebsd.org
In-Reply-To: <199507060128.LAA21203@godzilla.zeta.org.au> from "Bruce Evans" at Jul 6, 95 11:28:28 am
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 477       
Sender: current-owner@freebsd.org
Precedence: bulk

Bruce Evans writes:

> >	"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.

The problem is more widespread .. "rmdir foo/" fails and complains of "foo
is a directory" (!) and "rm -rf foo/" does likewise,

	michael