All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Rui Xiang <leo.ruixiang@gmail.com>
Cc: "Serge E. Hallyn" <serge@hallyn.com>,
	serge.hallyn@canonical.com,
	containers@lists.linux-foundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH RFC 0/5] Containerize syslog
Date: Mon, 26 Nov 2012 09:16:06 -0600	[thread overview]
Message-ID: <87sj7wwg21.fsf@xmission.com> (raw)
In-Reply-To: <50ACA05F.7080005@gmail.com> (Rui Xiang's message of "Wed, 21 Nov 2012 17:35:27 +0800")

Rui Xiang <leo.ruixiang@gmail.com> writes:

> On 2012-11-19 22:37, Serge E. Hallyn wrote:

>> I understand that user namespaces aren't 100% usable yet, but looking
>> long term, is there a reason to have the syslog namespace separate
>> from user namespace?
>
> Actually we don't have strong preference. We'll think more about it. Hope we can make
> consensus with Eric.

I hope I am not hard to work with.  My primary concern is reasonable
looking code and good long term maintainable semantics.

I really don't care in which namespace where we file the kernel log
statements.

I care much more about which kernel log print statements we want filed
differently.

Eric

  reply	other threads:[~2012-11-26 15:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  8:16 [PATCH RFC 0/5] Containerize syslog Rui Xiang
     [not found] ` <50A9EAD8.9090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-19  9:51   ` Eric W. Biederman
     [not found]     ` <874nklkjjm.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-07  9:03       ` Andrew Morton
2012-12-07  9:03         ` Andrew Morton
     [not found]         ` <20121207010355.c809b3f7.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2012-12-07 14:23           ` Serge Hallyn
2012-12-07 14:30             ` Glauber Costa
     [not found]               ` <50C1FD9D.5020703-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-12-07 18:05                 ` Eric W. Biederman
     [not found]                   ` <87r4n1buuw.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-11  8:25                     ` Glauber Costa
2012-12-11  8:25                   ` Glauber Costa
     [not found]                     ` <50C6EDF0.5060108-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-12-11 18:22                       ` Eric W. Biederman
     [not found]                         ` <87txrs30ur.fsf-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
2012-12-12  8:56                           ` Glauber Costa
2012-12-12  8:56                         ` Glauber Costa
     [not found]                           ` <50C846C7.5050904-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2012-12-12 20:08                             ` Eric W. Biederman
2012-12-07 18:21             ` Eric W. Biederman
2012-12-07 18:21             ` Eric W. Biederman
2012-11-19 14:37   ` Serge E. Hallyn
     [not found]     ` <20121119143702.GB4620-7LNsyQBKDXoIagZqoN9o3w@public.gmane.org>
2012-11-21  9:35       ` Rui Xiang
2012-11-26 15:16         ` Eric W. Biederman [this message]
     [not found]         ` <50ACA05F.7080005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-11-26 15:16           ` Eric W. Biederman

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=87sj7wwg21.fsf@xmission.com \
    --to=ebiederm@xmission.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=leo.ruixiang@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=serge.hallyn@canonical.com \
    --cc=serge@hallyn.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.