Messages in this thread | | | Subject | Re: [PATCH] unshare: Cleanup up the sys_unshare interface before we are committed. | From | (Eric W. Biederman) | Date | Mon, 20 Mar 2006 09:52:58 -0700 |
| |
"Albert Cahalan" <acahalan@gmail.com> writes:
> The unshare() syscall is in fact a clone() syscall minus one > CLONE_* flag that is normally implied: CLONE_TASK_STRUCT. > (conceptually -- it has no name because it is always implied) > > We already have one flag with inverted action: CLONE_NEWNS. > Adding another such flag (for the task struct) makes sense. > The new system call is thus not needed at all. > > Suggested names: CLONE_NO_TASK, CLONE_SAMETASK, CLONE_SHARETASK
The practical issue there is that even in the best case the implementations are enough different that it probably would not make a lot of sense.
Eric
- 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/
| |