From: Jeff Mahoney <jeffm@suse.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Joachim Reichelt <Reichelt@gbf.de>,
Nikita Danilov <Nikita@Namesys.COM>,
reiserfs-list@Namesys.COM
Subject: Re: Lost ACL
Date: Thu, 19 Feb 2004 12:33:37 -0500 [thread overview]
Message-ID: <4034F371.8000001@suse.com> (raw)
In-Reply-To: <4034EEB2.6090208@suse.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff Mahoney wrote:
| Joachim Reichelt wrote:
| |> i just got 2.4.25 up.
| |> But there is no ACL anywhere in the kernel.
| |> Do I have to patch something
| |> I found ACL in ext3, xfs....
| |> So there are NO ACLs in the code?????????
|
| ACLs and Extended Attributes are an external patch. The SuSE kernels
| have them by default, which is why you were able to use them with your
| SuSE install. Periodically, I sync up the ACL code with the mainline
| kernels.
|
| Expect an updated version for 2.4.25 later today on my ftp site:
| ftp://ftp.suse.com/pub/people/jeffm/reiserfs/aclea/
To follow up; The 2.4.23 patches apply cleanly to 2.4.24 and 2.4.25.
- -Jeff
- --
Jeff Mahoney
SuSE Labs
jeffm@suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFANPNxLPWxlyuTD7IRAt5XAKCVksCWf0+xWwJazaIlqLT5UiXfRQCeJrbx
5HZlQuQiM/AwfeJQ0Xqjl1k=
=ww5l
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-02-19 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:51 Lost ACL Joachim Reichelt
2004-02-13 18:44 ` Jeff Mahoney
2004-02-13 18:48 ` Nikita Danilov
2004-02-13 20:47 ` Jeff Mahoney
2004-02-19 16:56 ` Joachim Reichelt
2004-02-19 17:13 ` Jeff Mahoney
2004-02-19 17:33 ` Jeff Mahoney [this message]
2004-02-20 8:03 ` Joachim Reichelt
2004-02-20 8:07 ` Joachim Reichelt
2004-02-16 7:38 ` Joachim Reichelt
2004-02-19 17:29 ` Jeff Mahoney
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=4034F371.8000001@suse.com \
--to=jeffm@suse.com \
--cc=Nikita@Namesys.COM \
--cc=Reichelt@gbf.de \
--cc=reiserfs-list@Namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.