From: william@thinktankworkspaces.com
To: 9front@9front.org
Subject: Re: [9front] 9pfs
Date: Sat, 05 Oct 2024 09:26:10 -0700 [thread overview]
Message-ID: <D35CA899E4EEF2E7C8FD30D40DF243A1@thinktankworkspaces.com> (raw)
In-Reply-To: <fa52cff0-ab89-40cf-abed-2034429b0761@posixcafe.org>
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.
Quoth Jacob Moody <moody@posixcafe.org>:
> On 10/5/24 02:44, william@thinktankworkspaces.com wrote:
> > This is the one. I see the file now. So I'm missing a fuse library or fuse mount point mtpt?
> >
> > Quoth Jacob Moody <moody@posixcafe.org>:
> >> On 10/4/24 23:14, william@thinktankworkspaces.com wrote:
> >>> Usage: 9pfs [-anUfd] [-A aname] [-p port] [-u user] [-o option] service mtpt
> >>>
> >>> MacBook-Pro 9pfs % ./9pfs -o allow_other 9front /mnt
> >>> 9pfs: nodename nor servname provided, or not known
>
> I have no idea how fuse works on mac nor am I particularly interested in finding out,
> so all I can ask is you check that basics here.
>
> In this example you gave is '9front' a resolvable hostname? (ie can you 'ping 9front')
> Do you have port 564 listening on the 9front box?
> You're going to have to give a more full description of what you're trying to do.
>
>
next prev parent reply other threads:[~2024-10-05 16:29 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 [this message]
2024-10-05 17:46 ` Jacob Moody
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=D35CA899E4EEF2E7C8FD30D40DF243A1@thinktankworkspaces.com \
--to=william@thinktankworkspaces.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).