From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] remedial sources auth, connect, and mount in plan9port
Date: Thu, 1 Oct 2009 00:06:33 -0500 [thread overview]
Message-ID: <d50d7d460909302206j49097107idf2c3b4ece87b265@mail.gmail.com> (raw)
Geoff was kind enough to provide to me a contrib directory on sources,
so I'm now trying to write into it.
I can't seem to get the hang of the authorization, connection, and
mount steps necessary for an authorized mount of sources in plan9port,
so I can just copy files into my contrib directory. Over several
dozen attempts to understand factotum, it never saves any actual data
for me, so I apparently have some serious misunderstandings.
For the mount, I can use the following to mount sources read-only, but
I can't save anything into it.
sudo 9mount 'tcp!sources.cs.bell-labs.com' /n/sources
9fs sources also doesn't seem to provide an authenticated connection,
or a mount.
Would someone be kind enough to chant the few magic plan9(port)
incantations with which I can store my sources-server username and
password with factotum, connect to sources, and mount sources
(specifically, my directory) as a writable filesystem? I promise
diligent study, to understand what the commands do.
Jason Catena
next reply other threads:[~2009-10-01 5:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 5:06 Jason Catena [this message]
2009-10-01 7:44 ` Venkatesh Srinivas
2009-10-01 9:50 ` Jason Catena
2009-10-01 10:04 ` Ethan Grammatikidis
2009-10-01 10:31 ` sqweek
2009-10-01 12:38 ` Abhishek Kulkarni
2009-10-01 15:34 ` Jason Catena
[not found] <<d50d7d460910010834r40c926barbc3dedd5828f3bd1@mail.gmail.com>
2009-10-01 16:22 ` erik quanstrom
2009-10-02 3:03 ` Jason Catena
[not found] <<d50d7d460910012003h6aec0d3bj40ebdadac3358b6a@mail.gmail.com>
2009-10-02 3:11 ` erik quanstrom
2009-10-02 16:52 ` Jason Catena
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=d50d7d460909302206j49097107idf2c3b4ece87b265@mail.gmail.com \
--to=jason.catena@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).