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: <4AF2C000.3020807@redhat.com>
Date:	Thu, 05 Nov 2009 13:07:28 +0100
From:	Jan Safranek <jsafrane@...hat.com>
To:	Daniel Lezcano <daniel.lezcano@...e.fr>
CC:	balbir@...ux.vnet.ibm.com,
	libcg-devel <libcg-devel@...ts.sourceforge.net>,
	"menage@...gle.com" <menage@...gle.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	containers@...ts.linux-foundation.org,
	Bharata B Rao <bharata.rao@...ibm.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Dhaval Giani <dhaval@...ux.vnet.ibm.com>
Subject: Re: [RFC] Mount point suggestions for cgroup

On 11/04/2009 05:44 PM, Daniel Lezcano wrote:
> Balbir Singh wrote:
>> Hi, All,
>>
>> We've been having a discussion as to what would be the right place to
>> mount the cgroup filesystem. Jan has been proactively looking into
>> this. The FHS has no recommendation since cgroup filesystem came in
>> much later.
>>
>> The options are
>>
>> 1. /dev/cgroup
>> 2. /cgroup
>> 3. Some place under /sys
>>
>> The problem with (2) is that it is quite non-standard and pollutes the
>> root directory. (3) requires some basic support to create a directory
>> for cgroup under /sys. (1) seems the most obvious choice since cpusets
>> were mounted under /dev/cpuset, but /dev is controlled by udev.
>>
>> Given the three choices or any other suggestions, is there a general
>> preference as to where we can mount it? The goal is to standardize
>> the mount point (if possible).
> Why the mount point has to be standardized ?
>

The mount point does not need to be set into stone so everybody *must* 
use it. I, as Fedora packager, just need some default place where to 
mount it, so applications which need to create/manage groups work 
without any (potentially dumb) user assistance. Of course, advanced 
admin can change the settings and move the groups anywhere, applications 
still need to parse /proc/mounts or use appropriate library like libcgroup.

Jan
--
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