9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] wstat and atomic directory change
Date: Wed,  4 Feb 2015 16:30:15 +0000	[thread overview]
Message-ID: <CAJSxfmJL4KJqd+q1G4V_MeSs3KEpa6YQiHdtkvgrxtvLa0kePg@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psFXKXqs8HvuV2d-TWtb-u78+b25+UnK0VV2sWqRHGS01g@mail.gmail.com>

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

you can consider doing it out of band; e.g. a new fossil console command.
On Wed, Feb 4, 2015 at 6:30 AM Giacomo Tesio <giacomo@tesio.it> wrote:

> And unfortunately I cannot figure out any alternative, either. :-(
>
> An interesting point is: why directory entries can be read but cannot be
> written? I mean we use Tcreate to create a new file in a dir, while to be
> uniform with files, we should use a Twrite, appending a corresponding stat
> structure at the end of a directory entry.
>
> However this solution probably has not been adopted to enable safe
> concurrency in the file creation and removal.
>
> However this asymmetry shows that directories cannot be (pratically)
> handled in the same way of files.
>
>
> Giacomo
>
>
> 2015-02-04 15:06 GMT+01:00 erik quanstrom <quanstro@quanstro.net>:
>
>> > You are right.
>> > But since protocol customizations goes against that same ideal, what's
>> the
>> > plan9 way of dealing with a feature X (in this specific case atomic file
>> > moves)?
>> >
>> >
>> > > this requires delving into the namespace to tell that the directories
>> are
>> > > still under the
>> > > same mount, and some non-uniform operations.
>> > >
>> >
>> > Good point. But thus, what are the alternatives?
>>
>> i wasn't holding out.  i don't have any suggestions.
>>
>> - erik
>>
>>
>

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

  reply	other threads:[~2015-02-04 16:30 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
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 [this message]
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=CAJSxfmJL4KJqd+q1G4V_MeSs3KEpa6YQiHdtkvgrxtvLa0kePg@mail.gmail.com \
    --to=skip.tavakkolian@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).