public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Morris <jmorris@namei.org>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: David Wagner <daw-usenet@taverner.CS.Berkeley.EDU>,
	linux-kernel@vger.kernel.org
Subject: Re: understanding Linux capabilities brokenness
Date: Tue, 9 Aug 2005 00:46:19 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508090044400.20178@excalibur.intercode> (raw)
In-Reply-To: <20050809015048.GA14204@thunk.org>

Let me play the Devil's advocate here.

Should we be thinking about deprecating and removing capabilities from 
Linux?


- James
-- 
James Morris
<jmorris@namei.org>

  reply	other threads:[~2005-08-09  4:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 21:12 understanding Linux capabilities brokenness David Madore
2005-08-08 22:32 ` David Madore
2005-08-08 23:53   ` David Wagner
2005-08-09  1:50     ` Theodore Ts'o
2005-08-09  4:46       ` James Morris [this message]
2005-08-09  8:09         ` Jan Engelhardt
2005-08-09 15:16         ` Christopher Warner
2005-08-09 20:20           ` Kyle Moffett
2005-08-09  4:59       ` David Madore
2005-08-09  5:53         ` James Morris

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=Pine.LNX.4.63.0508090044400.20178@excalibur.intercode \
    --to=jmorris@namei.org \
    --cc=daw-usenet@taverner.CS.Berkeley.EDU \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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