From: Hans Reiser <reiser@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: using of XATTRs instead of pseudo files for accessing reiser4 file attributes.
Date: Mon, 05 Apr 2004 08:55:56 -0700 [thread overview]
Message-ID: <4071818C.4050609@namesys.com> (raw)
In-Reply-To: <20040405115439.GA1924@backtop.namesys.com>
We are not going to use xattrs, get that through your head.
Hans
Alex Zarochentsev wrote:
>Hello,
>
>Does anybody think that using linux extended attributes API would be good for
>accessing specific reiser4 file attributes?
>
>
>Currently all that stuff is exported through pseudo files under "metas"
>subdirectory. It might be good for scripting but it leads to security problems
>in legacy unix applications and it requires having +x permission on regular
>files or modifying linux VFS.
>
>It is not a problem to have two API for accessing file attributes, XATTR
>and pseudo files. At least XATTR will be usefull in places where security
>matters.
>
>Regards,
>Alex.
>
>
>
>
--
Hans
next prev parent reply other threads:[~2004-04-05 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 11:54 using of XATTRs instead of pseudo files for accessing reiser4 file attributes Alex Zarochentsev
2004-04-05 12:46 ` Chris Mason
2004-04-05 22:41 ` Alexander G. M. Smith
2004-04-06 1:22 ` Hubert Chan
2004-04-06 12:13 ` Chris Mason
2004-04-07 7:55 ` using of XATTRs instead of pseudo files for accessing mjt
2004-04-05 15:55 ` Hans Reiser [this message]
2004-04-05 17:54 ` using of XATTRs instead of pseudo files for accessing reiser4 file attributes Narcoleptic Electron
2004-04-05 18:10 ` Alex Zarochentsev
2004-04-05 18:19 ` Alex Zarochentsev
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=4071818C.4050609@namesys.com \
--to=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=zam@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.