From: "Björn JACKE" <bj@SerNet.DE>
To: Jeremy Allison <jra@samba.org>
Cc: Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>
Subject: Re: Displaying streams as xattrs
Date: Thu, 25 May 2023 11:39:00 +0200 [thread overview]
Message-ID: <20230525093900.GA261009@sernet.de> (raw)
In-Reply-To: <ZGuWhzP98U9Niog+@jeremy-rocky-laptop>
On 2023-05-22 at 09:21 -0700 Jeremy Allison via samba-technical sent off:
> On Mon, May 22, 2023 at 01:39:50AM -0500, Steve French wrote:
> > On Sun, May 21, 2023 at 11:33 PM ronnie sahlberg
> > <ronniesahlberg@gmail.com> wrote:
> > >
> > > A problem we have with xattrs today is that we use EAs and these are
> > > case insensitive.
> > > Even worse I think windows may also convert the names to uppercase :-(
> > > And there is no way to change it in the registry :-(
> >
> > But for alternate data streams if we allowed them to be retrieved via xattrs,
> > would case sensitivity matter? Alternate data streams IIRC are already
> > case preserving. Presumably the more common case is for a Linux user
> > to read (or backup) an existing alternate data stream (which are usually
> > created by Windows so case sensitivity would not be relevant).
>
> Warning Will Robinson ! Mixing ADS and xattrs on the client side is a receipe for
> confusion and disaster IMHO.
>
> They really are different things. No good will come of trying to mix
> the two into one client namespace.
>
just took a look at how the ntfs-3g module is handling this. It was an option
streams_interface=value, which allows "windows", which means that the
alternative data streams are accessable as-is like in Windows, with ":" being
the separator. This might be a nice option for cifsfs also. That option would
just be usable if no posix extensions are enabled of course.
Björn
next prev parent reply other threads:[~2023-05-25 10:01 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 [this message]
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
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=20230525093900.GA261009@sernet.de \
--to=bj@sernet.de \
--cc=jra@samba.org \
--cc=linux-cifs@vger.kernel.org \
--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