Michael Kerrisk <mtk.manpages@xxxxxxxxxxxxxx> writes: > Serge, Eric, > > Below is a patch to document the CLONE_NEWUTS flag that was > added in 2.6.19. > > Could you please review and let me know of improvements > or inaccuracies? > > By the way, does anyone know where the UTS name in the uname() > API comes from? My best guess is that it's from Unix Timesharing > System, but I don't know this for sure. > > Cheers, > > Michael > > diff --git a/man2/clone.2 b/man2/clone.2 > index 7212332..80f9caf 100644 > --- a/man2/clone.2 > +++ b/man2/clone.2 > @@ -341,6 +340,33 @@ configuration option and that the process be privileged > This flag can't be specified in conjunction with > .BR CLONE_THREAD . > .TP > +.BR CLONE_NEWUTS " (since Linux 2.6.19)" > +If > +.B CLONE_NEWUTS > +is set, then create the process in a new UTS namespace. > +If this flag is not set, then (as with > +.BR fork (2)), > +the process is created in the same UTS namespace as > +the calling process. > +This flag is intended for the implementation of control groups. See my previous email about containers vs control groups. There are some corner cases with NFS usage in the kernel that still need to be resolved but otherwise the uts namespace is considered correct and complete. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
