From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] 9pfs
Date: Sat, 5 Oct 2024 12:46:53 -0500 [thread overview]
Message-ID: <a5b7f15b-9c99-4024-be06-93ac98bec772@posixcafe.org> (raw)
In-Reply-To: <D35CA899E4EEF2E7C8FD30D40DF243A1@thinktankworkspaces.com>
On 10/5/24 11:26, william@thinktankworkspaces.com wrote:
> Oh I see. I do have a 9front server running. This is my first exeriment with 9pfs. I just wanted to
> throw 9pfs on a Mac and a few linux boxes. I guess I just wanted to connect without the hassel of
> ssh or sshfs. But it does sound like I need a few more tools to really get the benefit out of it
> beyond 9pfs, meaning that I suppose I need plan9ports installed and factotum and a few other things or is
> that incorrect. Strange enough but I'm kind of getting attached to acme editor and have been using it
> in my daily life with sshfs and changing code on remote servers. It's light weight as opposed to vscode
> or intellij running remotely which is heavy. I loose some benefits but I gain others.
>
> So I thought to kind of expand with 9pfs and take advantage of some additional features.
>
Hold on here, it's still not clear exactly what the end result is that you're looking for here.
Let's start from the top here:
9pfs does not require anything from plan9port.
9pfs is a fuse 9p client.
9pfs connects to a system that is running a 9p file server (over port 564 by default).
This means your mac is initiating a network connection to your 9front machine, so the 9front machine must be listening for 9p.
Ssh and sshfs go the other way, they initiate a network connection from 9front to a machine running ssh.
9pfs would expose the 9front's files to your mac, sshfs exposes your macs files to your 9front.
A 9front machine does not expose its root filesystem over 9p by default, that requires some modifications.
This is why I was asking about the networking status of your 9front machine (ie can you ping it, is it listening on port 564 etc)
Hope this helps,
moody
next prev parent reply other threads:[~2024-10-05 17:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 4:14 william
2024-10-05 5:12 ` Jacob Moody
2024-10-05 7:44 ` william
2024-10-05 16:01 ` Jacob Moody
2024-10-05 16:26 ` william
2024-10-05 17:46 ` Jacob Moody [this message]
2024-10-05 18:33 ` william
2024-10-05 19:56 ` Romano
2024-10-05 20:19 ` Aram Hăvărneanu
2024-10-06 0:05 ` william
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=a5b7f15b-9c99-4024-be06-93ac98bec772@posixcafe.org \
--to=moody@posixcafe.org \
--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).