From owner-freebsd-hackers@FreeBSD.ORG Fri Nov 6 16:03:00 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D94D51065676; Fri, 6 Nov 2009 16:03:00 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0016F8FC14; Fri, 6 Nov 2009 16:02:59 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,694,1249250400"; d="scan'208";a="17792038" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 06 Nov 2009 17:02:59 +0100 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id 130151B07BE; Fri, 6 Nov 2009 17:02:59 +0100 (CET) Date: Fri, 06 Nov 2009 17:02:58 +0100 (CET) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Alex Dupre , Alexander Best Message-ID: In-Reply-To: <4AF444AC.1030507@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: rmdir(2) and mkdir(2) both return EISDIR for argument "/" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Nov 2009 16:03:00 -0000 Alex Dupre schrieb am 2009-11-06: > Alexander Best ha scritto: > > thanks a lot for finding the problem in the src. what do you think > > of the > > patch attached to this message? > I'm sorry, but I haven't enough knowledge about this subsystem to > judge > your patch. Someone else should jump in. neither do i. ;) i fear the patch is just a dirty hack and probably breaks tons of conventions. ;) i'll post the patch as followup to the PR and see what happens. thanks again for having a look at the problem and pointing out the responsible code. alex