From: Jeremy Allison <jra@samba.org>
To: Steve French <smfrench@gmail.com>
Cc: ronnie sahlberg <ronniesahlberg@gmail.com>,
atheik <atteh.mailbox@gmail.com>,
Hyeoncheol Lee <hyc.lee@gmail.com>,
Namjae Jeon <linkinjeon@kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Tom Talpey <tom@talpey.com>
Subject: Re: [PATCH 1/2] ksmbd: update documentation
Date: Thu, 1 Sep 2022 14:48:39 -0700 [thread overview]
Message-ID: <YxEot6I5d4PWtrz9@jeremy-acer> (raw)
In-Reply-To: <CAH2r5mvUzbp8RcM7+XFbJsoiba964vpKQiMRmGeQovGabe+j=Q@mail.gmail.com>
On Thu, Sep 01, 2022 at 04:37:21PM -0500, Steve French wrote:
>
>I do like that Namjae et al made the format of the .conf file very similar
>to the format of Samba's smb.conf file though. I realize there some
>users complain that there are too many smb.conf parameters for Samba,
>but he seemed to pick a reasonably subset of them for ksmbd.
>Samba is a much larger project with many more smb.conf parameters
>but it does reduce confusion making the parameter names similar
>where possible e.g. "workgroup", "guest account", (share) path, read only, etc.
>and fortunately the default directories for the two smb.conf files are
>different so at least the daemons don't use the same file.
Sure, I think the formats and parameter names being as close
as possible is a great idea to allow users to move between
servers as they wish. But making the files the same name
is not a good idea.
next prev parent reply other threads:[~2022-09-01 21:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 14:17 [PATCH 1/2] ksmbd: update documentation Namjae Jeon
2022-08-30 14:17 ` [PATCH 2/2] ksmbd: remove generic_fillattr use in smb2_open() Namjae Jeon
2022-09-01 6:08 ` Hyunchul Lee
2022-08-30 16:13 ` [PATCH 1/2] ksmbd: update documentation Tom Talpey
2022-08-31 1:36 ` Namjae Jeon
2022-09-01 5:19 ` atheik
2022-09-01 13:06 ` Tom Talpey
2022-09-01 16:14 ` Jeremy Allison
2022-09-01 17:41 ` atheik
2022-09-01 18:30 ` Jeremy Allison
2022-09-01 18:52 ` Tom Talpey
2022-09-01 22:24 ` Steve French
2022-09-01 23:54 ` Tom Talpey
2022-09-01 19:42 ` atheik
2022-09-01 20:26 ` Jeremy Allison
2022-09-01 21:21 ` ronnie sahlberg
2022-09-01 21:37 ` Steve French
2022-09-01 21:48 ` Jeremy Allison [this message]
2022-09-02 0:56 ` Namjae Jeon
2022-09-02 2:11 ` Jeremy Allison
2022-09-02 12:35 ` Tom Talpey
2022-09-02 13:33 ` Namjae Jeon
2022-08-30 17:32 ` Tom Talpey
2022-08-31 0:02 ` Namjae Jeon
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=YxEot6I5d4PWtrz9@jeremy-acer \
--to=jra@samba.org \
--cc=atteh.mailbox@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=ronniesahlberg@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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