From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 2 21:30:07 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89CB316A418 for ; Thu, 2 Aug 2007 21:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 727E313C45D for ; Thu, 2 Aug 2007 21:30:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l72LU7ZA052226 for ; Thu, 2 Aug 2007 21:30:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l72LU7nd052225; Thu, 2 Aug 2007 21:30:07 GMT (envelope-from gnats) Date: Thu, 2 Aug 2007 21:30:07 GMT Message-Id: <200708022130.l72LU7nd052225@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Joe Peterson Cc: Subject: Re: kern/59739: [libc] rmdir(2) and mkdir(2) both return EISDIR for argument "/" X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Joe Peterson List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2007 21:30:07 -0000 The following reply was made to PR kern/59739; it has been noted by GNATS. From: Joe Peterson To: bug-followup@FreeBSD.org, asf@boinkor.net Cc: Subject: Re: kern/59739: [libc] rmdir(2) and mkdir(2) both return EISDIR for argument "/" Date: Thu, 02 Aug 2007 15:01:12 -0600 Hi, we at Gentoo/FreeBSD just ran into this issue with a script that had worked on Linux, since it expected EEXIST for all dirs (it did not expect EISDIR when trying to mkdir an existing dir when it hit "/"). We have fixed it, but since the mkdir/rmdir man pages do not specify EISDIR as a potential error code - and just for correctness/compatibility reasons - my feeling is that it would be good to fix this issue. I also have no experience hacking FreeBSD kernel or userland utilities, so I have not pursued providing a patch. Sorry if this follow-up is not useful without having a patch. -Thanks, Joe