9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Giacomo Tesio <giacomo@tesio.it>
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 16:59:33 +0100	[thread overview]
Message-ID: <CAHL7psEpfW7jESQ4qeqc9RA4jWWzJwugBPDiHhMWAa3jag0g0Q@mail.gmail.com> (raw)
In-Reply-To: <36c9016b7918c302d777f1a605fc107f@brasstown.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

It surely would not be conformant to Plan 9 systems, but to the protocol?

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".

Be patient: I'm asking because this could be a typo in the intro(5) man
page, or in my understanding of its phrasing.

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.


Giacomo


2015-01-30 15:13 GMT+01:00 erik quanstrom <quanstro@quanstro.net>:

> > Now, since the protocol does not restrict names (even if Plan 9 does it),
> > I'm wondering if setting the name to a full path starting from root could
> > be used to change atomically the directory of a file (given the write
> > permission on both original and target directory).
> >
> > Obviously I'm not referring to Plan 9 file servers (I guess this would
> be a
> > non retrocompatbile change), but I'm considering if such interpretation
> > would be wrong (according to the official specifications).
> >
> > A server supporting such behaviour could be considered a 9p2000
> conformant
> > server?
>
> it would not be conformant.  the intro explicitly excludes slash as a
> valid character.
> (unlike a dns zone.)  and its more detailed explinations are meant to hold
> for the
> entire section.
>
> but you could still do it, as long as the file servers were the same.
>
> - erik
>
>

[-- Attachment #2: Type: text/html, Size: 2132 bytes --]

  reply	other threads:[~2015-01-30 15:59 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 [this message]
2015-01-30 20:19     ` Joel C. Salomon
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=CAHL7psEpfW7jESQ4qeqc9RA4jWWzJwugBPDiHhMWAa3jag0g0Q@mail.gmail.com \
    --to=giacomo@tesio.it \
    --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).