From: Andreas Gruenbacher <agruen@suse.de>
To: linux-kernel@vger.kernel.org
Cc: Chris Mason <mason@suse.de>
Subject: [RFC][PATCH 0/3] Access Control Lists for tmpfs and /dev/pts
Date: Wed, 02 Feb 2005 17:13:40 +0100 [thread overview]
Message-ID: <20050202161340.660712000@blunzn.suse.de> (raw)
Here is a set of three patches which implement some general
infrastructure and on top of that, acls for tmpfs and /dev/pts files.
We may want to factor out some of the current ext2 and ext3 acl code
and use the generic layer instead. Comments welcome.
Regards,
--
Andreas Gruenbacher <agruen@suse.de>
SUSE Labs, SUSE LINUX PRODUCTS GMBH
next reply other threads:[~2005-02-02 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 16:13 Andreas Gruenbacher [this message]
2005-02-02 16:25 ` [RFC][PATCH 3/3] Access Control Lists for /dev/pts Andreas Gruenbacher
2005-02-02 16:25 ` [RFC][PATCH 2/3] Access Control Lists for tmpfs Andreas Gruenbacher
2005-02-02 16:29 ` [RFC][PATCH 1/3] Generic infrastructure for acls Andreas Gruenbacher
2005-02-02 16:55 ` [RFC][PATCH 0/3] Access Control Lists for tmpfs and /dev/pts Christoph Hellwig
2005-02-02 17:37 ` Andreas Gruenbacher
2005-08-04 19:39 ` Catalin Patulea
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=20050202161340.660712000@blunzn.suse.de \
--to=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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