From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Exclude System entries with "ls" or "find"
Date: Wed, 19 Dec 2018 20:57:00 -0000 [thread overview]
Message-ID: <7f296933-3536-19a6-77ff-b167215e7c7e@SystematicSw.ab.ca> (raw)
In-Reply-To: <623029685.20181219174321@yandex.ru>
On 2018-12-19 07:43, Andrey Repin wrote:
>> On Dec 19 08:29, Eliot Moss wrote:
>>> On 12/19/2018 7:10 AM, Andrey Repin wrote:
>>>>> Bottom line is, if you want to handle DOS attributes in a special way
>>>>> not covered by our POSIX emulation, user space has to do it.
>>>> Can something be implemented around getfattr to serve this use case in a more
>>>> POSIX'y way?
>>> I was not previously much aware of get/setfattr, but I agree that that looks
>>> like a possible way to provide access to the Windows SYS attribute and friends.
>>> Not that I am that familiar with details of what NTFS, etc., provide, getfattr
>>> may be a way to provide access to additional attributes / facts about files
>>> (paths, generally) as well. Sounds like it would not be too hard to support
>>> access to the basic attributes this way.
>>> I suspect the general response will be PTC, though! :-)
>> Not only that. attr is an upstream package, so you would have to
>> convince the upstream maintainers to take your patches, ideally.
>> attr is for handling of extended attributes, quite different from
>> DOS attributes. I doubt that DOS attribs fit in there.
> Well, well. We do have a living example of Samba (ab)using xattr to support
> Windows ACL on *NIX.
> I deduce from your response, that a DOS attributes use case would be on
> different side of the table, though.
While WSL uses Windows EAs to support POSIX stattributes[sic].
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
prev parent reply other threads:[~2018-12-19 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 8:13 Steven Penny
2018-12-18 12:58 ` Corinna Vinschen
2018-12-18 15:51 ` Eliot Moss
2018-12-18 16:19 ` cyg Simple
2018-12-19 1:10 ` Eliot Moss
2018-12-19 10:06 ` Brian Inglis
2018-12-19 12:20 ` Corinna Vinschen
2018-12-19 12:53 ` Andrey Repin
2018-12-19 13:37 ` Eliot Moss
2018-12-19 14:50 ` Corinna Vinschen
2018-12-19 15:19 ` Andrey Repin
2018-12-19 18:25 ` Corinna Vinschen
2018-12-19 20:57 ` Brian Inglis [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=7f296933-3536-19a6-77ff-b167215e7c7e@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).