Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751136AbWCRXlY (ORCPT ); Sat, 18 Mar 2006 18:41:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751138AbWCRXlY (ORCPT ); Sat, 18 Mar 2006 18:41:24 -0500 Received: from ozlabs.org ([203.10.76.45]:61598 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S1751136AbWCRXlY (ORCPT ); Sat, 18 Mar 2006 18:41:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17436.39580.217348.85222@cargo.ozlabs.ibm.com> Date: Sun, 19 Mar 2006 10:41:16 +1100 From: Paul Mackerras To: ebiederm@xmission.com (Eric W. Biederman) Cc: Linus Torvalds , Michael Kerrisk , akpm@osdl.org, linux-kernel@vger.kernel.org, janak@us.ibm.com, viro@ftp.linux.org.uk, hch@lst.de, ak@muc.de Subject: Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed. In-Reply-To: References: <29085.1142557915@www064.gmx.net> X-Mailer: VM 7.19 under Emacs 21.4.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 743 Lines: 19 Eric W. Biederman writes: > - We don't confuse users and developers about the inverted values of > the clone bits. Given that the name starts with "un", I would *expect* unshare(CLONE_FOO) to mean that I no longer want to share FOO. If you want the argument to have the same sense as in the clone system call, you will have to call it "share" rather than "unshare" (and then explain to confused developers why they can't use it to start sharing things that previously weren't shared :). Paul. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/