public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Pavel Fedin <p.fedin@samsung.com>
To: cygwin@cygwin.com
Subject: RE: Extended attributes
Date: Mon, 20 Jan 2014 05:22:00 -0000	[thread overview]
Message-ID: <006301cf159f$8c0c8d90$a425a8b0$%fedin@samsung.com> (raw)
In-Reply-To: <20140116091600.GC26205@calimero.vinschen.de>

 Hello!

> I'm really not inclined to add this.  As it is, the NTFS xattr are
> always treated as user attributes.  An NTFS attr "foo.bar" is returned
> as "user.foo.bar" and when writing, a "user.foo.bar" is written as
> "foo.bar".  Adding other attribute types requires to add some special
> casing and parsing code to differ user attributes from other attributes
> without breaking backward compatibility.
> 
> Also, it will never work correctly on a Samba share, because Samba will
> always treat the incoming attribute as above.  So, if you write an
> attribute "trusted.md5sum" on a samba share, it will actually be
> converted to "user.trusted.md5sum" by Samba.

 Sorry for late reply, too busy at work now... The same about NFS-related packages - no time ATM to make them... :(
 You know, i got your point, and perhaps this can be rethought. Perhaps this can be done on SquashFS side. For example, we could tell it to store 'security.foo' attribute as 'user.squashfs.security.foo'. This could be also useful on Linux, because in this case you don't have to be root any more to be able to prepare a rootfs for your embedded device.
 I think i'll consider that after i finish up with NFS.

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

      parent reply	other threads:[~2014-01-20  5:22 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
2014-01-16  9:16         ` Corinna Vinschen
2014-01-16 18:52           ` Christopher Faylor
2014-01-20  5:22           ` Pavel Fedin [this message]

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='006301cf159f$8c0c8d90$a425a8b0$%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).