From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Extended attributes
Date: Wed, 15 Jan 2014 09:15:00 -0000 [thread overview]
Message-ID: <20140115091530.GH10212@calimero.vinschen.de> (raw)
In-Reply-To: <002f01cf11ba$df28b550$9d7a1ff0$%fedin@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
On Jan 15 10:27, Pavel Fedin wrote:
> Hello!
>
> > "user." xattrs are supported, but no others. This is partially to have
> > smooth support of xattrs when using Samba shares. See the attr
> > package and the getxattr, etc. calls in Cygwin's ntea.cc.
>
> Yes, i have checked that.
> What do you think about adding other possible namespaces (system,
> security, and... don't remember the 3rd one) ? So that when
> manipulating UNIX archives etc these attributes could be kept along
> with files ? At least we have one use case now.
That doesn't make sense. Extended attributes as implemented by Windows
are user attributes, not system attributes. The non-user attributes
on Linux have a very special meaning to the kernel and/or are restricted
to privileged users only. Their functionality is already provided by
other OS functions (as for system.posix_acl_access) or not at all (as
for security.selinux).
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-01-15 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 13:53 Pavel Fedin
2014-01-13 14:10 ` Corinna Vinschen
2014-01-15 6:27 ` Pavel Fedin
2014-01-15 9:15 ` Corinna Vinschen [this message]
2014-01-16 6:08 ` Pavel Fedin
2014-01-16 9:16 ` Corinna Vinschen
2014-01-16 18:52 ` Christopher Faylor
2014-01-20 5:22 ` Pavel Fedin
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=20140115091530.GH10212@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).