From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] wstat and atomic directory change
Date: Thu, 5 Feb 2015 10:59:20 +0200 [thread overview]
Message-ID: <4b124b3339c2c26f28c75ffc17bd70cb@proxima.alt.za> (raw)
In-Reply-To: <CAHL7psGC9oA59N2qmu+GOaGEqSB9RCy+ceVcNk+OMu+S9iUhPA@mail.gmail.com>
> I'm not an advocate of Tmove in any way, but I can't really grasp the cons.
> I'm sure that its omission was an explicit design choise, but where I
> can read about the arguments that lead to such decision?
It's a long time ago, but I seem to recall that the clinching argument
hinged around mounted directories. Without making an a priori
decision about each one, an atomic move is not viable. Remember that
to the OS the difference between a local and a remote object is
intentionally invisible.
And then you need to add per-user and per-process namespaces...
Lucio.
next prev parent reply other threads:[~2015-02-05 8: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
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 [this message]
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=4b124b3339c2c26f28c75ffc17bd70cb@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).