From: "Björn JACKE" <bj@sernet.de>
To: Jeremy Allison <jra@samba.org>, Steve French <smfrench@gmail.com>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
Christoph Hellwig <hch@lst.de>, CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: Displaying streams as xattrs
Date: Fri, 26 May 2023 00:14:49 +0200 [thread overview]
Message-ID: <20230525221449.GA9932@sernet.de> (raw)
In-Reply-To: <ZG/DajG6spMO6A7v@jeremy-rocky-laptop>
On 2023-05-25 at 13:22 -0700 Jeremy Allison sent off:
> I think cifsfs providing access to ADS remotely on Windows
> and Samba shares is fine.
>
> What I'm scared of is adding ADS as a generic "feature" to
> the Linux VFS and other filesystems :-).
full ack on Jeremy's view here.
If there is something the the Linux VFS layer should *really* add to help
interopearbility with basically all other major OS implementations is NFSv4
ACLs. Seriously, for so many people living with Linux is a real pain due to
the lack of NFS4 ACLs here.
Björn
>
next prev parent reply other threads:[~2023-05-25 22:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 2:08 Displaying streams as xattrs Steve French
2023-05-22 4:33 ` ronnie sahlberg
2023-05-22 6:39 ` Steve French
2023-05-22 14:41 ` ronnie sahlberg
2023-05-22 16:21 ` Jeremy Allison
2023-05-23 0:59 ` ronnie sahlberg
2023-05-23 2:23 ` Andrew Walker
2023-05-23 16:25 ` Jeremy Allison
2023-05-23 21:44 ` ronnie sahlberg
2023-05-23 22:34 ` Jeremy Allison
2023-05-25 10:57 ` ronnie sahlberg
2023-05-25 16:15 ` Jeremy Allison
2023-05-26 2:39 ` ronnie sahlberg
2023-05-26 16:20 ` Jeremy Allison
2023-05-25 9:39 ` Björn JACKE
2023-05-25 10:49 ` ronnie sahlberg
2023-05-25 16:22 ` Jeremy Allison
2023-05-25 20:11 ` Steve French
2023-05-25 20:22 ` Jeremy Allison
2023-05-25 22:14 ` Björn JACKE [this message]
2023-05-25 23:50 ` Steve French
2023-05-26 2:16 ` ronnie sahlberg
2023-05-26 16:03 ` Björn JACKE
[not found] ` <CAH2r5muD89QUcaqWNQy5NUwyji9CinN_5kGcfFSQAbpJP5gn+A@mail.gmail.com>
2023-05-27 1:50 ` Steve French
2023-05-30 7:26 ` Michael Weiser
2023-05-22 15:36 ` Andrew Walker
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=20230525221449.GA9932@sernet.de \
--to=bj@sernet.de \
--cc=hch@lst.de \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.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