From: jhf@rivenstone.net (Joseph Fannin)
To: linux-kernel@vger.kernel.org
Subject: An AOL for ext[23] ea/acl support
Date: Wed, 30 Oct 2002 14:56:09 -0500 [thread overview]
Message-ID: <20021030195609.GA20295@rivenstone.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=unknown-8bit, Size: 781 bytes --]
I want to say I hope very much that the extended attribute and
access control lists patches for ext2 and ext3 go into the kernel
before the feature freeze. I've been running and using Andreas
Grünbacher's patches for 2.4 for around a year now, setting ACLs on
files in SAMBA shares from Windows NT clients. It's very useful, and
given me no trouble at all.
ACL support for SAMBA is a common reason given on the linux-xfs
list by people using XFS -- it's a feature desired by more people than
me -- and it can be configured out of the kernel if anyone is very
worried about their data.
Wow, that's a really inopertune signature.
--
Joseph Fannin
jhf@rivenstone.net
"Linus, please apply. Breaks everything. But is cool." -- Rusty Russell.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2002-10-30 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021030195609.GA20295@rivenstone.net \
--to=jhf@rivenstone.net \
--cc=linux-kernel@vger.kernel.org \
/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