public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Josselin Mouette <joss@debian.org>
To: debian-devel@lists.debian.org,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: cgroup mount point
Date: Wed, 04 Feb 2009 10:16:21 +0100	[thread overview]
Message-ID: <1233738981.4045.4.camel@shizuru> (raw)
In-Reply-To: <20090204003847.308cd0df@sbs173>

[-- Attachment #1: Type: text/plain, Size: 758 bytes --]

Le mercredi 04 février 2009 à 00:38 +0100, Harald Braumann a écrit :
> So, what's the problem with /dev/cgroups then? If shm/ and pts/
> are allowed under /dev, wouldn't it be discriminating against
> cgroups/, to not allow it there?

/dev/pts contains device entries, so it sounds right to put it in /dev.
Similarly if the cgroups FS provides facilities to control some system
settings, it clearly belongs in /sys.

(/dev/shm is another story, and if you asked me, I’d have put it
in /lib/shm instead, but it’s a bit late to change it.)

-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

[-- Attachment #2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2009-02-04 10:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090202200013.GU3643@vespa.holoscopio.com>
     [not found] ` <1233606371.15779.32.camel@radis.liafa.jussieu.fr>
     [not found]   ` <20090202205246.GA28593@glandium.org>
2009-02-02 21:41     ` cgroup mount point Thadeu Lima de Souza Cascardo
2009-02-02 22:54       ` Chris Friesen
2009-02-02 23:43         ` Thadeu Lima de Souza Cascardo
2009-02-03  3:15         ` KAMEZAWA Hiroyuki
2009-02-03  5:06           ` Serge E. Hallyn
2009-02-06  6:17           ` Balbir Singh
2009-02-03 10:24       ` Daniel P. Berrange
2009-02-03 12:30         ` Thadeu Lima de Souza Cascardo
2009-02-03 13:26           ` Daniel P. Berrange
     [not found]         ` <87ljsnzo4v.fsf@benfinney.id.au>
2009-02-03 12:57           ` Thadeu Lima de Souza Cascardo
2009-02-04  3:59             ` Ben Finney
2009-02-03 14:38           ` Gustavo Noronha
2009-02-03 16:55             ` Paul Menage
2009-02-03 18:49               ` Mike Hommey
2009-02-03 18:51                 ` sean finney
2009-02-03 19:14                   ` Paul Menage
2009-02-03 23:38                     ` Harald Braumann
2009-02-03 23:40                       ` Paul Menage
2009-02-04  0:18                         ` Harald Braumann
2009-02-04  9:16                       ` Josselin Mouette [this message]
2009-02-05 21:19                       ` José Luis Tallón
2009-02-06 22:00                         ` Harald Braumann
2009-02-03 15:03         ` Gabor Gombas
2009-02-03 16:19           ` Bill Nottingham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1233738981.4045.4.camel@shizuru \
    --to=joss@debian.org \
    --cc=debian-devel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox