All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: -o noposixpaths
Date: Mon, 11 Jul 2011 13:48:20 -0500	[thread overview]
Message-ID: <CAH2r5mvR3E=E066MckaLVjpvwbcWg8BEvH+gtzpF-BSYaLvZUw@mail.gmail.com> (raw)
In-Reply-To: <20110711144146.3748d1ff-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>

On Mon, Jul 11, 2011 at 1:41 PM, Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
> On Mon, 11 Jul 2011 13:32:54 -0500
> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> Yes, IIRC the apple guys mentioned plausible server scenarios for this
>> (where we want to mount with unix extensions for symlinks and ownership
>> but server can not handle posix path names)
>>
>> Presumably if the server file system does not support posix path names
>> (FAT32, NTFS?) or if we want to restrict the characters (for interoperability
>> with Windows clients accessing the same share?) - might be other cases.
>>
>
> In that case though, shouldn't those servers just not set
> CIFS_UNIX_POSIX_PATHNAMES_CAP ?

I don't think servers do that (unset the POSIX_PATHNAMES CAP for one
share and not others, even assuming the share exports all volumes
of the same file system type)  for the former case
(unless they cant support posix path at all for the whole server),
and for the latter case, not sure that the server can know enough
information (about other clients which may mount the system)
to unset the CAP unilaterally.



-- 
Thanks,

Steve

  parent reply	other threads:[~2011-07-11 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11 18:23 -o noposixpaths Jeff Layton
     [not found] ` <20110711142311.27b4dfce-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-07-11 18:32   ` Steve French
     [not found]     ` <CAH2r5mv3WOCKk4jL1YXrfvSjt52NOTgJZKatbLqB4U61iuZxRg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-11 18:41       ` Jeff Layton
     [not found]         ` <20110711144146.3748d1ff-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2011-07-11 18:48           ` Steve French [this message]
     [not found]             ` <CAH2r5mvR3E=E066MckaLVjpvwbcWg8BEvH+gtzpF-BSYaLvZUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-07-11 19:06               ` Jeff Layton

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='CAH2r5mvR3E=E066MckaLVjpvwbcWg8BEvH+gtzpF-BSYaLvZUw@mail.gmail.com' \
    --to=smfrench-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.