From: Jeff Layton <jlayton@redhat.com>
To: steve <steve@steve-ss.com>
Cc: samba@lists.samba.org, linux-cifs@vger.kernel.org,
samba-technical@lists.samba.org, smfrench@gmail.com
Subject: Re: CIFS: Deprecating NFS mounting syntax in mount.cifs
Date: Tue, 23 Oct 2012 13:02:38 -0400 [thread overview]
Message-ID: <20121023130238.6100255d@corrin.poochiereds.net> (raw)
In-Reply-To: <5086CA29.8030305@steve-ss.com>
On Tue, 23 Oct 2012 18:47:37 +0200
steve <steve@steve-ss.com> wrote:
> On 10/23/2012 05:56 PM, Scott Lovenberg wrote:
> > On 10/18/2012 2:07 PM, scott.lovenberg@gmail.com wrote:
> > no one has objected (or really said anything). Can we merge this patch?
> > --
> Hi
> I'm just trying to represent users. Can we take this to user level by
> giving an example of what will work and what will not work after the patch?
>
> For example, the Linux automounter.
>
> Currently, we have this map:
> * -fstype=cifs,rw,sec=krb5 ://myserver/myshare/&
>
Does that really work? What purpose does the ':' serve there? That
should probably be removed. I doubt we'd end up breaking that syntax,
but I can't be certain.
> Are you talking about the difference between that and this:
> * -fstype=cifs,rw,sec=krb5 myserver:/myshare/&
Right, the above syntax would no longer work after the change.
>
> Question: will I need to change anything due to this patch?
>
For this patch, you don't need to do anything. It just adds a warning.
Eventually though, nfs-style "devicenames" would no longer work for
cifs mounts. For your map above, you probably want something like:
* -fstype=cifs,rw,sec=krb5 //myserver/myshare/&
(i.e. get rid of the extraneous ':').
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2012-10-23 17:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 18:07 CIFS: Deprecating NFS mounting syntax in mount.cifs scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1350583669-12118-1-git-send-email-scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-18 18:07 ` [PATCH] Add warning that NFS syntax is deprecated and will be removed in cifs-utils-6.0 scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w
[not found] ` <1350583669-12118-2-git-send-email-scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-10-23 19:40 ` Jeff Layton
2012-10-23 15:56 ` CIFS: Deprecating NFS mounting syntax in mount.cifs Scott Lovenberg
2012-10-23 16:47 ` steve
2012-10-23 17:02 ` Jeff Layton [this message]
[not found] ` <20121023130238.6100255d-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-10-23 17:22 ` steve
[not found] ` <5086D258.1020203-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2012-10-23 17:32 ` Scott Lovenberg
2012-10-23 17:36 ` Jeff Layton
[not found] ` <20121023133627.798100fb-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-10-24 6:47 ` steve
[not found] ` <5086CA29.8030305-dZ4O0aZtNmBWk0Htik3J/w@public.gmane.org>
2012-10-23 17:27 ` Scott Lovenberg
[not found] ` <CAFB9KM26Qk-MC+_w-Q4Rrg3X0nMJ2efS72Y+GjWckgf9g6fzEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-23 19:23 ` steve
2012-10-24 6:20 ` Scott Lovenberg
-- strict thread matches above, loose matches on Subject: below --
2012-10-18 17:50 scott.lovenberg-Re5JQEeQqe8AvxtiuMwx3w
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=20121023130238.6100255d@corrin.poochiereds.net \
--to=jlayton@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=samba-technical@lists.samba.org \
--cc=samba@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=steve@steve-ss.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