From: Andreas Gruenbacher <agruen@suse.de>
To: Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] 2.5.42 (2/2): Filesystem capabilities user tool
Date: Sun, 27 Oct 2002 14:55:28 +0100 [thread overview]
Message-ID: <200210271455.28569.agruen@suse.de> (raw)
In-Reply-To: <87smz3mupw.fsf@goat.bogus.local>
On Friday 18 October 2002 21:07, Olaf Dietsche wrote:
> This is the change capabilities tool. It is a first cut at "managing"
> capabilities and not very comfortable.
Olaf, please start with reading the capabilities sections in POSIX
1003.1e/1003.2c draft 17 (withdrawn). There It's available online at
<http://wt.xpilot.org/publications/posix.1e/>. A number of people have
already spent a lot of time figuring out how this could work.
--Andreas.
prev parent reply other threads:[~2002-10-27 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:07 [PATCH][RFC] 2.5.42 (2/2): Filesystem capabilities user tool Olaf Dietsche
2002-10-24 12:31 ` [PATCH][RFC] 2.5.44 " Olaf Dietsche
2002-10-27 13:55 ` Andreas Gruenbacher [this message]
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=200210271455.28569.agruen@suse.de \
--to=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf.dietsche#list.linux-kernel@t-online.de \
/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