9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: fgergo@gmail.com
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] spec in plan9port?
Date: Tue, 6 Sep 2022 09:26:40 +0200	[thread overview]
Message-ID: <CA+ctqrroay4FwUTvLODt4=Vj+RuJ4niv9hLEGmqmRmLrFME8bg@mail.gmail.com> (raw)
In-Reply-To: <584A4CCE066B55E5EDF1850AD9DE6008@eigenstate.org>

On 9/5/22, ori@eigenstate.org <ori@eigenstate.org> wrote:
> Quoth fgergo@gmail.com:
>> On plan9 (and inferno) mount has [ spec ] to select between different
>> file trees:
>> https://9p.io/magic/man2html/1/bind
>> ...
>> mount [ option ... ] servename old [ spec ]
>> ...
>> "The spec argument to mount is passed in the attach(5) message to the
>> server, and selects among different file trees served by the server.
>> ...
>>
>> After looking at the source for srv(4), 9pserve(4) I am not sure this
>> is possible in plan9port. If yes, could somebody please share an
>> example?
>> thanks!
>>
>
> The spec comes in a form of a Tattach message to the file server,
> the muxers don't really have anything to do with it.
>

Sure, thanks for clarifying! Where else is or could be the passing of
spec to Tattach implemented?
Could you please give an example to mount /archive or /snapshot of a
serving fossil using plan9port if that's implemented?

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4d821c657f5e5431-M9e3a5e8d9856ac3217c63d40
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2022-09-06  7:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 12:05 fgergo
2022-09-05 19:54 ` ori
2022-09-06  7:26   ` fgergo [this message]
2022-09-06 13:08     ` ori
2022-09-06 14:32       ` fgergo
2022-09-06 14:41         ` ori

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='CA+ctqrroay4FwUTvLODt4=Vj+RuJ4niv9hLEGmqmRmLrFME8bg@mail.gmail.com' \
    --to=fgergo@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).