From: Jeremy Allison <jra-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org>
To: Richard Sharpe
<realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel
<linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Alternate Data Streams
Date: Mon, 2 Apr 2012 10:23:46 -0700 [thread overview]
Message-ID: <20120402172346.GA6980@samba2> (raw)
In-Reply-To: <CACyXjPyZGATA9vixXjG=O8FrTg6Aeb7Ew2jf_rKWqDhd5LW=1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Apr 02, 2012 at 10:21:31AM -0700, Richard Sharpe wrote:
> On 4/2/12, Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > A user was asking about how to query alternate data streams of files
> > (over cifs) remotely for backup.
> >
> > Alternate Data Streams can be read from cifs (e.g.
> > /path/filename:streamname) but not listed or created. Any thoughts
> > about whether this (at least listing the streams) should be done via
> > an ioctl, xattr or ...?
>
> Well, FindFirstStreamW and FindNextStreamW seem to available from
> W2K03 on. There is a code project out there that you can search on. I
> hit it as the first link returned when I searched for "Enumerating
> Alternate Data Streams"
Remember Alternate Data Streams are dead from ReFS-onwards (thank
god :-).
next prev parent reply other threads:[~2012-04-02 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH2r5mvOTo47SQ-aJSiEZvaZaoxeZWRXt0wa=BuiOOJXfHxHXg@mail.gmail.com>
2012-04-02 17:21 ` Alternate Data Streams Richard Sharpe
[not found] ` <CACyXjPyZGATA9vixXjG=O8FrTg6Aeb7Ew2jf_rKWqDhd5LW=1A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-02 17:23 ` Jeremy Allison [this message]
2012-04-02 17:26 ` Richard Sharpe
2012-04-02 17:45 ` simo
[not found] ` <1333388705.2983.79.camel-akOVU7JyYd8WIfilqQrPtNi2O/JbrIOy@public.gmane.org>
2012-04-02 17:51 ` Richard Sharpe
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=20120402172346.GA6980@samba2 \
--to=jra-eunubhrolfbytjvyw6ydsg@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=realrichardsharpe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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 NNTP newsgroup(s).