From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Andy Lutomirski <luto@myrealbox.com>
Cc: Chris Wright <chrisw@osdl.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] capabilities, take 3 (Re: [PATCH] capabilites, take 2)
Date: Sat, 15 May 2004 17:50:31 +0200 [thread overview]
Message-ID: <87y8ntk7ug.fsf@goat.bogus.local> (raw)
In-Reply-To: 40A4D49C.3030300@myrealbox.com
Andy Lutomirski <luto@myrealbox.com> writes:
> BTW, in your capabilities implementation, why do you do:
There's no such thing like "my" capabilities implementation. I use the
capabilities implementation of linux main line as it is. My patch
provides the possibility to connect capabilities to files, nothing
else.
I never tried to fix or modify, how capabilities work.
> If the answer's because that's how Linux cap evolution works, then
> I'd say that Linux cap evolution is broken.
Well, it works for me. :-)
Regards, Olaf.
prev parent reply other threads:[~2004-05-15 15:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 20:08 [PATCH] capabilites, take 2 Andy Lutomirski
2004-05-14 1:20 ` Chris Wright
2004-05-14 1:35 ` Valdis.Kletnieks
2004-05-14 4:51 ` Chris Wright
2004-05-14 5:33 ` Olaf Dietsche
2004-05-14 6:04 ` Valdis.Kletnieks
2004-05-14 7:09 ` Olaf Dietsche
2004-05-14 2:27 ` Andy Lutomirski
2004-05-14 4:48 ` Chris Wright
2004-05-14 5:58 ` Andy Lutomirski
2004-05-14 17:45 ` Chris Wright
2004-05-14 6:39 ` Olaf Dietsche
2004-05-14 2:45 ` [PATCH] capabilities, take 3 (Re: [PATCH] capabilites, take 2) Andy Lutomirski
2004-05-14 5:04 ` Chris Wright
2004-05-14 5:32 ` Valdis.Kletnieks
2004-05-14 5:40 ` Chris Wright
2004-05-14 6:25 ` Valdis.Kletnieks
2004-05-14 11:10 ` Olaf Dietsche
2004-05-14 14:15 ` Andy Lutomirski
2004-05-15 15:50 ` Olaf Dietsche [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=87y8ntk7ug.fsf@goat.bogus.local \
--to=olaf+list.linux-kernel@olafdietsche.de \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox