| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20090121132337.9ff4ed16.kamezawa.hiroyu@jp.fujitsu.com> Date: Wed, 21 Jan 2009 13:23:37 +0900 From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> To: ebiederm@...ssion.com (Eric W. Biederman) Cc: Sukadev Bhattiprolu <sukadev@...ux.vnet.ibm.com>, oleg@...hat.com, roland@...hat.com, bastian@...di.eu.org, daniel@...ac.com, xemul@...nvz.org, containers@...ts.osdl.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/7][v7] Container-init signal semantics On Tue, 20 Jan 2009 20:16:40 -0800 ebiederm@...ssion.com (Eric W. Biederman) wrote: > KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> writes: > > > What makes me confused is "Container". There is no "Container" in > > the linux kernel, just cgroup and its subsyss. > > (Some source codes still use "cont" but new codes all use "cgroup" or "cgrp" ) > > > > So, I asked whether "Container" means "Namespace subsys" or something different. > > "Container" is what we use to refer to the user space concept, that is built > from a set of namespaces and control groups. A Container that looks like > a standard linux install from the inside is what we expect the most common > use of namespaces and control groups to be. > Thank you for clarification :) Regards, -Kame -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists