On Mon, Aug 08, 2005 at 03:46:06PM +0100, Alan Cox wrote: > On Llu, 2005-08-08 at 09:33 -0400, Janak Desai wrote: > > > > [PATCH 1/2] unshare system call: System Call handler function sys_unshare > > > Given the complexity of the kernel code involved and the obscurity of > the functionality why not just do another clone() in userspace to > unshare the things you want to unshare and then _exit the parent ?
Because you want to keep children? Because you don't want to deal with the implications for sessions/groups/etc.? FWIW, syscall makes sense. It is a valid primitive and the only reason to keep it out of clone() (i.e. not making it just another flag to clone()) is that clone() is already cluttered _and_ uses bad calling conventions for that stuff ("I want to retain <list>" rather than "I want private <list>"). - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/