All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Lovenberg <scott.lovenberg@gmail.com>
To: steve <steve@steve-ss.com>
Cc: samba@lists.samba.org, linux-cifs@vger.kernel.org,
	samba-technical@lists.samba.org, jlayton@redhat.com,
	smfrench@gmail.com
Subject: Re: CIFS: Deprecating NFS mounting syntax in mount.cifs
Date: Wed, 24 Oct 2012 02:20:10 -0400	[thread overview]
Message-ID: <CAFB9KM2bTnsA1jnMR26r+Why=gVNE0qwoaXvbpQfmSZy+yMd=Q@mail.gmail.com> (raw)
In-Reply-To: <5086EE9C.7030800@steve-ss.com>

On Tue, Oct 23, 2012 at 3:23 PM, steve <steve@steve-ss.com> wrote:

> Hi Scott, hi everyone
> Yeah, that's fine.
> Does this clear up the issue with the ':'? I should have made it clearer
> that I was referring to autofs and not mounting e.g. from fstab. I just
> tried the automounter on cifs without the ':' and it doesn't work.
>
> Would it perhaps help to put a message in the logs when it fails, rather
> than silence? Or maybe that's more of a question for the autofs guys.
> Cheers,
> Steve
>

I've been at home thinking about this for a while tonight. I've
checked the documentation for autofs and they do what they say what
they'll do with that path (treat anything without a ':' as an NFS
mount).  On our side, (mount.cifs) we do what we say we'll do (support
UNC paths).  The most we could ask of them is to add/modify their
documentation to include the case for CIFS instead of just SMB.

This doesn't change anything on the mount.cifs side other than
explicitly directing users to the correct syntax for CIFS shares when
using autofs.  Ultimately the autofs documentation implicitly states
that CIFS shares should use a ':'.

All that being said, the mount.cifs has never officially supported NFS
path syntax.  We aren't silently ignoring the issue; we're sending a
warning to stdout that in a future version of the mount utility we
won't support this undocumented behavior.  To be fair, that's more
than most code bases do for deprecating undocumented features.

If anyone wants me to pursue the issue, I'll see what I can do about
getting the documentation for autofs altered to explicitly mention
CIFS paths.  I think that is reasonable for everyone.  It's after 2 AM
in my part of the world, so I'll do this tomorrow after my first cup
of coffee if anyone requests it.

-- 
Peace and Blessings,
-Scott.

  reply	other threads:[~2012-10-24  6:20 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
     [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 [this message]
  -- 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='CAFB9KM2bTnsA1jnMR26r+Why=gVNE0qwoaXvbpQfmSZy+yMd=Q@mail.gmail.com' \
    --to=scott.lovenberg@gmail.com \
    --cc=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 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.