From: NightStrike <nightstrike@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Support for ADS (Alternate Data Streams)
Date: Sat, 8 Jan 2022 04:14:35 -0500 [thread overview]
Message-ID: <CAF1jjLvKD5DXzgev3-JbtZ-wG5XWipRkJjEmhyTupnCcxWyp7g@mail.gmail.com> (raw)
In-Reply-To: <YdVtz7nup9JvZc7M@calimero.vinschen.de>
On Wed, Jan 5, 2022, 05:08 Corinna Vinschen <corinna-cygwin@cygwin.com>
wrote:
> On Jan 3 22:40, NightStrike wrote:
> > On Sun, Jan 2, 2022, 15:51 <cygwin@kosowsky.org> wrote:
> >
> > > While I recognize that ADS is not supported by POSIX, I was wondering
> > > what if any support for ADS might exist within Cygwin.
> > >
> > > The last time I looked into this was probably more than a decade ago
> > > but I am seeing (unfortunately) more usage of ADS in the Windows
> > > world, so I was wondering if there has been any effort to support in
> > > Cygwin?
> > >
> > > --
> > > Problem reports: https://cygwin.com/problems.html
> > > FAQ: https://cygwin.com/faq/
> > > Documentation: https://cygwin.com/docs.html
> > > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
> >
> >
> > FWIW, ntfs-3g under Linux maps these to extended attributes
>
> Using the EA API as ntfs-3g with the streams_interface=xattr option
> seems like a nice way to allow reading and writing ADS on Cygwin as
> well.
>
> Do you know how ntfs-3g performs the mapping? For instance, I guess
> that ADS are stored in the user.* namespace? Does listxattr list ADS or
> does it skip them? Stuff like that.
>
The ntfs.streams.list attribute contains the stream names, and there's a
shortcut to access them by name with a colon. So if you have a stream named
str and a file named f.txt, you could do 'cat f.txt:str'.
next prev parent reply other threads:[~2022-01-08 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 20:50 cygwin
2022-01-02 23:06 ` Thomas Wolff
2022-01-02 23:23 ` cygwin
2022-01-04 3:40 ` NightStrike
2022-01-05 10:07 ` Corinna Vinschen
2022-01-08 9:14 ` NightStrike [this message]
2022-01-10 9:27 ` 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=CAF1jjLvKD5DXzgev3-JbtZ-wG5XWipRkJjEmhyTupnCcxWyp7g@mail.gmail.com \
--to=nightstrike@gmail.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).