From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] attr 2.4.48-2
Date: Fri, 21 Dec 2018 07:13:00 -0000 [thread overview]
Message-ID: <20181220222241.GA3310@calimero.vinschen.de> (raw)
In-Reply-To: <792facca-bc23-d5c0-76af-336a95e455c1@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Dec 20 09:03, Brian Inglis wrote:
> On 2018-12-20 03:04, Corinna Vinschen wrote:
> > The following packages have been uploaded to the Cygwin distribution:
> >
> > * attr-2.4.48-2
> > * libattr-devel-2.4.48-2
> > * libattr1-2.4.48-2
>
> Does this release support listing Windows Alternate Data Streams, as the Linux
> release does with Tuxera NTFS-3G?
libattr only supports reading and writing EAs, it has no capabilities to
read or write ADS. Ntfs-3g supports the streams_interface=windows
option which allows to read ADS. This also adds the ntfs.streams.list
EA to a file with named ADS. So attr/getfattr can only inspect the
ntfs.streams.list EA because the NTFS-3G driver creates them on the fly
when inspecting the file EAs.
tl;dr: No, sorry. This could only work if Cygwin fakes the
ntfs.streams.list EA per file just like the NTFS-3G driver.
Patches welcome. Looks like a nice little project if you want to get
your hands dirty. The functions to handle EAs are pretty
self-sufficiently implemented in ntea.cc. A little loop about
NtQueryInformationFile(FileStreamInformation) should do it.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-12-20 22:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 10:47 Corinna Vinschen
2018-12-20 22:22 ` Brian Inglis
2018-12-21 7:13 ` Corinna Vinschen [this message]
2019-01-08 11:29 ` Corinna Vinschen
2019-01-08 15:36 ` Brian Inglis
2019-01-08 16:21 ` Corinna Vinschen
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=20181220222241.GA3310@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).