From: Dominik Kubla <dominik.kubla@uni-mainz.de>
To: Nick Cabatoff <ncc@cs.mcgill.ca>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] HFS linux implementation
Date: Fri, 10 Mar 2000 23:28:02 +0100 [thread overview]
Message-ID: <20000310232802.A6578@uni-mainz.de> (raw)
In-Reply-To: <20000310010949.A14656@cs.mcgill.ca>; from Nick Cabatoff on Fri, Mar 10, 2000 at 01:09:49AM -0500
On Fri, Mar 10, 2000 at 01:09:49AM -0500, Nick Cabatoff wrote:
> Actually, it looks like just stock UFS with ACL support, as far as I can
> see. Even that's kind of optional; many sites don't use ACLs at all
> (hell, dump/restore don't know about them), and it looks like a
> read-only implementation that just ignored them would work fine. I
> think that would be almost too easy given the existing linux UFS module
> though, so once that much is working I'll probably do a writeable
> version that preserves ACLs, even if it doesn't allow you to work with
> them.
Well, just talk to the linux-acl folks... they are just pushing the
(former ext2) ACL stuff up into the VFS, in order to have a generic
API to access the filesystem specific ACL implementations. Unfortunately
the ACL development still lingers in 2.2 territory, but that's no excuse
not to think ahead and at least add the hooks for it when one touches
a file system anyway.
Web pages are at: http://acl.bestbits.at/
Mailing list is at: http://acl.bestbits.at/acl-devel/
Dominik
--
Networking Group, Hospital of Johannes Gutenberg-University
Obere Zahlbacher Straße 69, 55101 Mainz, Germany
Tel: +49 (0)6131 17-2482 FAX: +49 (0)6131 17-5521
next prev parent reply other threads:[~2000-03-10 23:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-10 0:35 [parisc-linux] HFS linux implementation Nick Cabatoff
2000-03-10 1:37 ` Grant Grundler
2000-03-10 6:09 ` Nick Cabatoff
2000-03-10 7:30 ` Grant Grundler
2000-03-10 22:28 ` Dominik Kubla [this message]
2000-03-10 8:33 ` Martin K. Petersen
2000-03-10 15:59 ` Nick Cabatoff
2000-03-10 16:04 ` willy
2000-03-10 16:35 ` Nick Cabatoff
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=20000310232802.A6578@uni-mainz.de \
--to=dominik.kubla@uni-mainz.de \
--cc=ncc@cs.mcgill.ca \
--cc=parisc-linux@thepuffingroup.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