9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Joel C. Salomon" <joelcsalomon@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] wstat and atomic directory change
Date: Fri, 30 Jan 2015 15:19:35 -0500	[thread overview]
Message-ID: <CAFUtaNGhOWzv+p9wyXO5Xi4B+QZNvQDdh=L_B7x1gPCyM4XJJA@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psEpfW7jESQ4qeqc9RA4jWWzJwugBPDiHhMWAa3jag0g0Q@mail.gmail.com>

On Fri, Jan 30, 2015 at 10:59 AM, Giacomo Tesio <giacomo@tesio.it> wrote:
> As far as I can read intro(5), it explicitly excludes slash as a valid
> character for the Plan 9 OS, but it also explicitly states that "the
> protocol has no such restriction".

My reading is that a 9p2000 server might allow a filename of the form
"b/c"; e.g. this tree is possible:

    a
    |-- b
    |   +-- c
    |       +-- d
    +-- b/c
        +-- d

Note that "a" / "b" / "c" / "d" is distinct from "a" / "b/c" / "d".
Plan 9, because of its Unix heritage, will not be able to deal with
this, but the protocol has no such limitation. On the other hand, if
you bypass the OS and issue a Walk to "a/b/c/d", there is a
well-defined response required in the protocol -- either open the file
with that (impossible) name, or fail.

> Still, using this protocol "feature" to enable atomic directory change could
> be useful in my use cases, but I don't want to build yet another 9p2000
> extension.

It'll have to be an extension -- a technically incompatible one,
though the incompatibilities will not ever happen.

--Joel



  reply	other threads:[~2015-01-30 20:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 11:21 Giacomo Tesio
2015-01-30 14:13 ` erik quanstrom
2015-01-30 15:59   ` Giacomo Tesio
2015-01-30 20:19     ` Joel C. Salomon [this message]
2015-01-30 22:49     ` Anthony Sorace
2015-02-03  8:53       ` Giacomo Tesio
2015-02-03  9:04         ` Quintile
2015-02-04  3:51           ` erik quanstrom
2015-02-04  8:28             ` Giacomo Tesio
2015-02-04 14:06               ` erik quanstrom
2015-02-04 14:29                 ` Giacomo Tesio
2015-02-04 16:30                   ` Skip Tavakkolian
2015-02-04 19:23                     ` erik quanstrom
2015-02-04 21:24                       ` Giacomo Tesio
2015-02-05  4:13                         ` lucio
2015-02-05  8:21                           ` Giacomo Tesio
2015-02-05  8:37                             ` Giacomo Tesio
2015-02-05  8:59                               ` lucio
2015-02-05  8:54                             ` lucio
2015-02-05 16:13                               ` erik quanstrom
2015-02-05  4:15                         ` lucio
2015-02-05 16:20                         ` erik quanstrom
2015-02-05 16:46                           ` Giacomo Tesio
2015-02-05 17:22                             ` Skip Tavakkolian
2015-02-05 17:20                           ` Bakul Shah
2015-02-05  4:26 sl
2015-02-05  4:26 sl
2015-02-05  8:08 ` Giacomo Tesio

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='CAFUtaNGhOWzv+p9wyXO5Xi4B+QZNvQDdh=L_B7x1gPCyM4XJJA@mail.gmail.com' \
    --to=joelcsalomon@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).