mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thadeu Lima de Souza Cascardo <cascardo@minaslivre.org>
To: Ben Finney <ben+debian@benfinney.id.au>
Cc: debian-devel@lists.debian.org, linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org
Subject: Re: cgroup mount point
Date: Tue, 3 Feb 2009 10:57:45 -0200	[thread overview]
Message-ID: <20090203125744.GC3788@vespa.holoscopio.com> (raw)
In-Reply-To: <87ljsnzo4v.fsf@benfinney.id.au>

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

On Tue, Feb 03, 2009 at 11:44:00PM +1100, Ben Finney wrote:
> "Daniel P. Berrange" <berrange@redhat.com> writes:
> 
> > On Mon, Feb 02, 2009 at 07:41:53PM -0200, Thadeu Lima de Souza Cascardo wrote:
> > > So, we have some more options now: /cgroups, /containers,
> > > /dev/cpuset, /dev/cpuctl, /opt/cgroup, /opt/cpuset.
> > 
> > Putting new mount points in / is not really acceptable, so that rules
> > out the first two. /opt is just totally wrong, since that is intended
> > for add on software packages. /dev/ feels a little odd, since it is
> > not really device nodes
> 
> I agree with all that Thadeu Lima says here. I would add that cgroups
> are nothing to do with device nodes, so definitely don't belong in
> ‘/dev/’ either.

The message you quoted is from Daniel Berrange, not me. Could you also
tell your rationale for not agreeing with /?

Regards,
Cascardo.

> Since they're a filesystem mapping “for browsing and manipulation
> from user space” of a kernel facility, I think ‘/sys/cgroups/’ is
> appropriate.
> 
> -- 
>  \     “It's my belief we developed language because of our deep inner |
>   `\                  need to complain.” —Jane Wagner, via Lily Tomlin |
> _o__)                                                                  |
> Ben Finney

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-02-03 12:57 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     ` 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 [this message]
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
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=20090203125744.GC3788@vespa.holoscopio.com \
    --to=cascardo@minaslivre.org \
    --cc=ben+debian@benfinney.id.au \
    --cc=containers@lists.linux-foundation.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

all inboxes | Powered by JetHome®