From: stefncb@gmail.com
To: 9front@9front.org
Subject: Re: [9front] File sharing with Windows
Date: Wed, 22 Jun 2022 07:14:33 +0300 [thread overview]
Message-ID: <111F5A2248B474E79463963F5CBEF03E@yourdomain.dom> (raw)
In-Reply-To: <9ba67fc0-5e00-1066-fbbb-700a2e656ec6@riseup.net>
Quoth mkf9 <mkf9@riseup.net>:
> stefncb@gmail.com wrote:
>
> > I've looked at the manpage, which lead me to listen(8), saying that it's supposed to be ran by tcp445 - which does contain a call to cifsd. I'm scratching my head on how I'm supposed to correctly configure and use that service. I mean, it's there, what do I do to make it actually run?
>
>
> change /bin/service/!tcp445, rename it to tcp445 and run
> % aux/listen
> then it should listen for it.
>
> or use aux/listen1 instead, without need of dealing with files under
> /bin/service
I changed /rc/bin/service/!tcp445 to:
#!/bin/rc
exec /bin/ip/cifsd -f /sys/log/cifsd.debug -w WORKGROUP -o trspaces $*
(The only thing I thought made sense to change was the workgroup, it now matches the Windows PC).
And then ran aux/listen. Am I supposed to find a new network share on the Windows PC now? I don't.
Jacob mentioned SMBv3 support, but going through the Windows features I could enable SMBv1/CIFS support, which didn't help.
I thought I should check the debug log - /sys/log/cifsd.debug doesn't even exist. How do I check if the service is actually running?
next prev parent reply other threads:[~2022-06-22 7:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 12:52 stefncb
2022-06-21 16:02 ` Jacob Moody
2022-06-21 15:20 ` stefncb
2022-06-21 18:34 ` mkf9
2022-06-21 18:37 ` Jacob Moody
2022-06-22 4:14 ` stefncb [this message]
2022-06-22 7:44 ` mkf9
2022-06-22 5:26 ` stefncb
2022-06-22 8:36 ` Frank D. Engel, Jr.
2022-06-22 5:51 ` stefncb
2022-06-22 9:01 ` Frank D. Engel, Jr.
2022-06-22 9:12 ` stefncb
2022-06-22 11:38 ` Steve Simon
2022-06-22 11:43 ` mkf9
2022-06-22 11:47 ` Steve Simon
2022-06-22 11:47 ` stefncb
2022-06-22 14:23 ` cinap_lenrek
2022-06-22 14:49 ` Steve Simon
2022-06-22 16:57 ` sirjofri
2022-06-22 17:42 ` Marshall Conover
2022-06-22 20:28 ` Steve Simon
2022-06-21 16:07 ` Marshall Conover
2022-06-21 15:21 ` stefncb
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=111F5A2248B474E79463963F5CBEF03E@yourdomain.dom \
--to=stefncb@gmail.com \
--cc=9front@9front.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).