From: Nix <nix@esperi.org.uk>
To: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6.13: Filesystem capabilities 0.16
Date: Fri, 02 Sep 2005 14:47:09 +0100 [thread overview]
Message-ID: <87fysnmvj6.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <87ll2ghb95.fsf@goat.bogus.local> (Olaf Dietsche's message of "1 Sep 2005 19:52:27 +0100")
On 1 Sep 2005, Olaf Dietsche murmured woefully:
> This patch implements filesystem capabilities. It allows to run
> privileged executables without the need for suid root.
Is there some reason why this doesn't keep its capability data in
xattrs?
--
`... published last year in a limited edition... In one of the
great tragedies of publishing, it was not a limited enough edition
and so I have read it.' --- James Nicoll
next prev parent reply other threads:[~2005-09-02 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 18:51 [PATCH] 2.6.13: Filesystem capabilities 0.16 Olaf Dietsche
2005-09-02 13:47 ` Nix [this message]
2005-09-03 0:35 ` serue
2005-09-03 19:25 ` Olaf Dietsche
2005-09-03 19:21 ` Olaf Dietsche
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=87fysnmvj6.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf+list.linux-kernel@olafdietsche.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