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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111104113646.5c0e9be6.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Fri, 4 Nov 2011 11:36:46 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	Daniel Lezcano <daniel.lezcano@...e.fr>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	mk@...all.com,
	"containers@...ts.linux-foundation.org" 
	<containers@...ts.linux-foundation.org>,
	nishimura@....nes.nec.co.jp, oleg@...hat.com,
	Michal Hocko <mhocko@...e.cz>,
	"hannes@...xchg.org" <hannes@...xchg.org>, tj@...nel.org,
	cgroups@...r.kernel.org, akpm@...ux-foundation.org,
	fweisbec@...il.com, paul@...lmenage.org
Subject: Re: [PATCH] add new cgroup list to CC notice

On Fri, 04 Nov 2011 03:09:31 +0100
Daniel Lezcano <daniel.lezcano@...e.fr> wrote:

> On 11/04/2011 01:40 AM, KAMEZAWA Hiroyuki wrote:
> > As discussed at Kernel Summit(2011), new cgroups mailing list is opened by
> > James. This list is for discussing general cgroup design and patches
> > including all subsystems and for getting more attentions to cgroups/namespaces
> > related issues by developpers.
> >
> > Signed-off-by: KAMEZAWA Hiroyuki<kamezawa.hiroyu@...fujitsu.com>
> > ---
> 
> I don't see the point to unilaterally change the mailing list to 
> vger.kernel.org as the discussions will be  the same as the actual 
> mailing list containers@. May be there is a good reason to do that but I 
> don't see it, can someone enlight me please ?
> 
I know containers@ and subscribing it.

Maybe this article is good.
http://lwn.net/Articles/464288/

I think there are cgroups not-for-container but total view/interaction
are required. someones may use cgroup just as resource controller (as libvirt,
systemd) and not be intereted in container itself.

I personally think cgroups@ is a straightforward name to kernel developpers. 

Thanks,
-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

Powered by Openwall GNU/*/Linux Powered by OpenVZ