From: Tom Talpey <tom@talpey.com>
To: Namjae Jeon <linkinjeon@kernel.org>, linux-cifs@vger.kernel.org
Cc: smfrench@gmail.com, senozhatsky@chromium.org, atteh.mailbox@gmail.com
Subject: Re: [PATCH v3] ksmbd: update documentation
Date: Mon, 12 Sep 2022 16:38:22 -0700 [thread overview]
Message-ID: <a5f680f2-6dc3-1c0b-bfbb-51f740e09109@talpey.com> (raw)
In-Reply-To: <20220909092558.9498-2-linkinjeon@kernel.org>
On 9/9/2022 5:25 AM, Namjae Jeon wrote:
> configuration.txt in ksmbd-tools moved to ksmbd.conf manpage.
> update it and more detailed ksmbd-tools build method.
>
> Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
> Signed-off-by: Namjae Jeon <linkinjeon@kernel.org>
> ---
> v3:
> - replace CIFS with SMB3 clients.
> - update ksmbd built-in case.
> - replace smb.conf leftover with ksmbd.conf.
> - use full name of utils in ksmbd-tools instead of <foo>.
> - fix the warnings from make htlmdocs build reported by kernel test
> robot.
> v2:
> - rename smb.conf to ksmbd.conf.
> - add how to set ksmbd module in menuconfig
> - remove --syscondir option for configure, instead change ksmbd
> directory to /usr/local/etc/ksmbd.
> - change the prompt to '$'.
>
> Documentation/filesystems/cifs/ksmbd.rst | 40 +++++++++++++++++-------
> 1 file changed, 29 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/filesystems/cifs/ksmbd.rst b/Documentation/filesystems/cifs/ksmbd.rst
> index 1af600db2e70..4284341c89f3 100644
> --- a/Documentation/filesystems/cifs/ksmbd.rst
> +++ b/Documentation/filesystems/cifs/ksmbd.rst
> @@ -118,26 +118,44 @@ ksmbd/nfsd interoperability Planned for future. The features that ksmbd
> How to run
> ==========
>
> -1. Download ksmbd-tools and compile them.
> - - https://github.com/cifsd-team/ksmbd-tools
> +1. Download ksmbd-tools(https://github.com/cifsd-team/ksmbd-tools/releases) and
> + compile them.
> +
> + - Refer README(https://github.com/cifsd-team/ksmbd-tools/blob/master/README.md)
> + to know how to use ksmbd.mountd/adduser/addshare/control utils
> +
> + $ ./autogen.sh
> + $ ./configure --with-rundir=/run
> + $ make && sudo make install
>
> 2. Create user/password for SMB share.
>
> - # mkdir /etc/ksmbd/
> - # ksmbd.adduser -a <Enter USERNAME for SMB share access>
> + - See ksmbd.adduser manpage.
> +
> + $ man ksmbd.adduser
> + $ sudo ksmbd.adduser -a <Enter USERNAME for SMB share access>
> +
> +3. Create /usr/local/etc/ksmbd/ksmbd.conf file, add SMB share in ksmbd.conf file.
I missed this in the v2 match - are you intentionally moving the
ksmbd.conf file to /usr/local/etc? That seems a very mysterious
location. Nothing on my vanilla installed system places anything
in there.
Also, doesn't this file need to exist before step 2??
Tom.
> -3. Create /etc/ksmbd/smb.conf file, add SMB share in smb.conf file
> - - Refer smb.conf.example and
> - https://github.com/cifsd-team/ksmbd-tools/blob/master/Documentation/configuration.txt
> + - Refer ksmbd.conf.example in ksmbd-utils, See ksmbd.conf manpage
> + for details to configure shares.
>
> -4. Insert ksmbd.ko module
> + $ man ksmbd.conf
>
> - # insmod ksmbd.ko
> +4. Insert ksmbd.ko module after build your kernel. No need to load module
> + if ksmbd is built into the kernel.
> +
> + - Set ksmbd in menuconfig(e.g. $ make menuconfig)
> + [*] Network File Systems --->
> + <M> SMB3 server support (EXPERIMENTAL)
> +
> + $ sudo modprobe ksmbd.ko
>
> 5. Start ksmbd user space daemon
> - # ksmbd.mountd
>
> -6. Access share from Windows or Linux using CIFS
> + $ sudo ksmbd.mountd
> +
> +6. Access share from Windows or Linux SMB3 clients (cifs.ko or smbclient of samba)
>
> Shutdown KSMBD
> ==============
next prev parent reply other threads:[~2022-09-12 23:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:25 [PATCH v2] ksmbd: fix incorrect handling of iterate_dir Namjae Jeon
2022-09-09 9:25 ` [PATCH v3] ksmbd: update documentation Namjae Jeon
2022-09-12 23:38 ` Tom Talpey [this message]
2022-09-12 23:54 ` Namjae Jeon
2022-09-13 19:02 ` Tom Talpey
2022-09-14 10:36 ` Namjae Jeon
2022-09-14 11:09 ` Atte Heikkilä
2022-09-15 18:25 ` Tom Talpey
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=a5f680f2-6dc3-1c0b-bfbb-51f740e09109@talpey.com \
--to=tom@talpey.com \
--cc=atteh.mailbox@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=senozhatsky@chromium.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