On Tue, Feb 21, 2006 at 07:29:17PM +0300, Kirill Korotaev wrote:
>>>I would prefer:
>>>- sys_ns_create()
>>> creates namespace and makes a task to inherit this namespace.
>>> If _needed_, it _can_ fork inside.
>>I don't see why not have both, the auto-created
>>*space on clone() and the ability to create empty
>>*spaces which can be populated and/or entered
>Can you give more details on what you mean by auto-created *space and
>empty *space?
>I see no much difference...
good, in this case we can drop the empty/standalone
*space and 'just' use the clone() one. glad that
we finally agree here ....
>>>- sys_ns_inherit()
>>> change active namespace.
>>hmm, sounds like a misnomer to me ...
>sys_ns_change ? :)
personally I prefer to see it as either enter or
move, but change is probably fine too (except for
the fact that it doesn't change the namespace)
>>>But how should we reference namespace? by globabl ID?
>>definitely by some system-unique identifier ...
>Should it be integer or path as Eric proposes?
IMHO the pointer would be sufficient, of course
this can be mapped to arbitrary names/int/etc ...
> Thanks,
> Kirill
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
