From: Atticus <grobe0ba@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Connect plan9 with Linux SMB resource
Date: Sun, 10 Apr 2022 05:18:55 -0500 [thread overview]
Message-ID: <CAJiDx7mQTK8JY=yGofrPqvJR0r-qCXtJhK=hpQsyU=hagMO4mg@mail.gmail.com> (raw)
In-Reply-To: <CAMCFwYyf+djTmbUJPtVKwhz8_XUq-6LnbskPLFcDFJtcciqTHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
I get failures when cifs(4) attempts protocol negotiation with Samba
4.14.12 on OpenBSD 7-stable, Windows 10, and Server 2019.
cifs(4) itself hasn't seen any commits since 2019, and may be awfully
out-of-date compared to the latest rubbish out of Redmond. I'm also not
aware of anyone that actually uses it regularly.
With Samba you may be able to tweak the protocol version and authentication
stuff, but I wouldn't count on that working, especially not in a domain
configuration.
If you just need to move files back and forth between your desktop and your
9front system, drawterm handles that by making the local system available
under /mnt/term.
There are also 9p servers available that can provide that service as well,
such as https://github.com/Harvey-OS/ninep/cmd/ufs which is written in Go,
so works on basically all major platforms.
There is also an NFS client and server available in 9front which may serve
your needs as well.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T48d3c6dc9120b30c-M95e13ae64ab101941e9e020e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1809 bytes --]
next prev parent reply other threads:[~2022-04-10 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 7:45 Tomás S. Javaloyes
2022-04-10 9:15 ` mkf9
2022-04-10 9:46 ` Tomás S. Javaloyes
2022-04-10 10:18 ` Atticus [this message]
2022-04-10 10:58 ` Tomás S. Javaloyes
2022-04-10 11:22 ` [9fans] factotum (was: Connect plan9 with Linux SMB resource) sirjofri
2022-04-10 12:14 ` Tomás S. Javaloyes
2022-04-10 14:05 ` Steve Simon
2022-04-10 17:39 ` Tomás S. Javaloyes
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='CAJiDx7mQTK8JY=yGofrPqvJR0r-qCXtJhK=hpQsyU=hagMO4mg@mail.gmail.com' \
--to=grobe0ba@gmail.com \
--cc=9fans@9fans.net \
/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).