From: Pavel Fedin <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: RE: Extended attributes
Date: Thu, 16 Jan 2014 06:08:00 -0000 [thread overview]
Message-ID: <001701cf1281$5fc57150$1f5053f0$%fedin@samsung.com> (raw)
In-Reply-To: <20140115091530.GH10212@calimero.vinschen.de>
Hello!
> > 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).
I know they have special meaning. At the other hand, if we allow them, we will allow to store them on a filesystem. Wouldn't it be nice ? This is useful at least for SquashFS image preparation.
I guess for similar reasons we have support e. g. for device nodes (/dev) with their major/minor numbers. They are also ignored by Cygwin, and just stored on the filesystem (or do i miss something ?).
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-01-16 6:08 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
2014-01-16 6:08 ` Pavel Fedin [this message]
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='001701cf1281$5fc57150$1f5053f0$%fedin@samsung.com' \
--to=p.fedin@samsung.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).