From: thinktankworkspaces@gmail.com
To: 9front@9front.org
Subject: Re: [9front] sshfs
Date: Tue, 28 Jul 2020 21:45:53 -0700 [thread overview]
Message-ID: <0BDE451923AF0745F87D944ADBF9FE4C@gmail.com> (raw)
In-Reply-To: <B3438636-3661-4646-9F5E-6E0446D2B794@stanleylieber.com>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
Right the manpages kind of poorly writen. Should have an example usage.
The flags should be listed similar to item of a list rather than hunt
them down.
It really starts out confusing.
If -c is specified, sshfs will instead launch thecommand specified by cmdline and if -p is specified, sshfs communicates with an SFTP server via stdin and stdout
I guess I go with -p
Unless -M is specified, sshfs will mount itself at the mountpoint specified by mtpt. Okay so I need mount point
cpu% sshfs -p williamgunnells@172.27.0.68 -m /Users/williamgunnells
\x05\x01\x03
.
sshfs: received garbage
cpu% sshfs -p -d williamgunnells@172.27.0.68 -m $home/sshdir
SFTP --> SSH_FXP_INIT
\x05\x01\x03
Why make it more complicated.
see bind(1)) with -c. -a and -b have the save function as they do with
mount. What?
So now I have to look at bind(1)
Does that have -a -b
Yes -b Both files must be directories. Add the new directory to the Beginning of the union directory represented by the old file
oh and -a is end of the untion
Hmm I wonder if there is an example in bind(1)
NOPE
It does have an example of mount /srv/boo /n/dump dump
sounds logical
What does that have to do with sshfs again now. I forgot
[-- Attachment #2: Type: message/rfc822, Size: 3962 bytes --]
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] sshfs
Date: Tue, 28 Jul 2020 23:33:02 -0400
Message-ID: <B3438636-3661-4646-9F5E-6E0446D2B794@stanleylieber.com>
On July 28, 2020 10:43:16 PM EDT, thinktankworkspaces@gmail.com wrote:
>So glad to have plan9 with email working.
>
>So what am I doing wrong with sshf here now that I can copy and paste
>my problem.
>
>
>cpu% sshfs williamgunnells@172.27.0.68:/Users/williamgunnells
>$home/sshdir
>ssh: dial: cs: can't translate service
>sshfs: read: eof
>cpu%
i'm not at a computer, but the usage suggests your syntax may be invalid:
; sshfs usage: sshfs [-abdRUG] [-s service] [-m mtpt] [-u uidfile] [-g gidfile] [-- ssh-options] [user@]host sshfs [-abdRUG] [-s service] [-m mtpt] [-u uidfile] [-g gidfile] -c cmdline sshfs [-abdRUG] [-s service] [-m mtpt] [-u uidfile] [-g gidfile] -p
check the man page for more information:
http://man.9front.org/4/sshfs
sl
next prev parent reply other threads:[~2020-07-29 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 2:43 sshfs thinktankworkspaces
2020-07-29 3:33 ` [9front] sshfs Stanley Lieber
2020-07-29 4:45 ` thinktankworkspaces [this message]
2020-07-29 5:21 ` Anthony Martin
2020-07-29 5:49 ` thinktankworkspaces
2020-07-29 5:24 ` Alex Musolino
2020-07-29 6:03 ` thinktankworkspaces
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=0BDE451923AF0745F87D944ADBF9FE4C@gmail.com \
--to=thinktankworkspaces@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).