From: "J. Bruce Fields" <bfields@fieldses.org>
To: Cedric Blancher <cedric.blancher@gmail.com>
Cc: "Theodore Ts'o" <tytso@mit.edu>, Richard Yao <ryao@gentoo.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Making an interface for alternative data streams
Date: Mon, 21 Mar 2016 20:12:55 -0400 [thread overview]
Message-ID: <20160322001255.GA2353@fieldses.org> (raw)
In-Reply-To: <CALXu0UdPyhBpOb-q-jpVN55d5unAQYXQFSm7HgNKWBH0Q_-gmg@mail.gmail.com>
On Mon, Mar 21, 2016 at 11:48:04PM +0100, Cedric Blancher wrote:
> Old invalid argument, and Sophos and Symatec look there as well.
>
> If it was a bad idea, why has Linux fs attributes which are almost the
> same as O_XATTR except that they use a custom api? Why does Macos have
> alternate streams (called forks)? Why did Solaris adopt it long ago
> (and still gets support questions about it - just saying before
> someone argues that no one uses THAT)?
Could you point us at some of those users?
--b.
next prev parent reply other threads:[~2016-03-22 0:12 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 18:11 Making an interface for alternative data streams Richard Yao
2016-03-21 18:18 ` Christoph Hellwig
2016-03-21 18:51 ` Richard Yao
2016-03-21 19:17 ` Richard Yao
2016-03-21 20:19 ` Richard Yao
2016-03-21 20:40 ` J. Bruce Fields
2016-03-21 22:36 ` Theodore Ts'o
2016-03-21 22:48 ` Cedric Blancher
2016-03-22 0:12 ` J. Bruce Fields [this message]
2016-03-22 1:02 ` Richard Yao
2016-03-22 2:21 ` Richard Yao
2016-03-22 16:15 ` Richard Sharpe
2016-03-22 20:08 ` J. Bruce Fields
2016-03-22 20:13 ` Richard Sharpe
2016-03-22 20:32 ` J. Bruce Fields
2016-03-22 21:42 ` Jeremy Allison
2016-03-23 4:13 ` Steve French
2016-03-23 4:19 ` Steve French
2016-03-23 14:45 ` Steve French
2016-03-23 17:01 ` Jeremy Allison
2016-03-23 17:16 ` Steve French
2016-03-23 15:16 ` J. Bruce Fields
2016-03-22 2:01 ` Richard Yao
2016-03-22 21:29 ` Dave Chinner
2016-03-22 21:52 ` J. Bruce Fields
2016-03-22 22:50 ` Dave Chinner
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=20160322001255.GA2353@fieldses.org \
--to=bfields@fieldses.org \
--cc=cedric.blancher@gmail.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=ryao@gentoo.org \
--cc=tytso@mit.edu \
/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).