From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9pfuse and O_APPEND
Date: Fri, 19 Dec 2008 11:49:59 -0800 [thread overview]
Message-ID: <F82C3E5D-D4C2-402A-948B-B2DBA766A6EC@sun.com> (raw)
In-Reply-To: <dd6fe68a0812190023h282af5bar6b1358d451dd45e3@mail.gmail.com>
On Dec 19, 2008, at 12:23 AM, Russ Cox wrote:
> Append-only and exclusive-use are properties of files
> and need to be enforced uniformly across all clients
> to be meaningful. They must be per-file, not per-fd.
Two questions:
1. But before I ask this one: I don't deny that per-file append-only
is *extremely* useful. My question is a different one: what is
the danger of N clients accesing the file X in append-only mode
and M clients accesing it in random access mode? Could you,
please, give a concrete scenario?
2. Could you, please, answer the question in the original email
of whether the kind of trivial patch (for the real thing you also
need
to handle O_APPEND in the fusecreate) I provided would be
acceptable
for the inclusion into Hg? I have no problem maintaining the
extra code
on the side, but if the change is deemed *not*
to be acceptable that translates into it being dangerous or not
good
enough. And if that's the case I'd really appreciate an
explanation to
be given.
Thanks,
Roman.
next prev parent reply other threads:[~2008-12-19 19:49 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 23:34 Roman Shaposhnik
2008-12-18 23:57 ` Russ Cox
2008-12-19 0:03 ` ron minnich
2008-12-19 3:06 ` Roman Shaposhnik
2008-12-19 3:26 ` ron minnich
2008-12-19 3:59 ` Roman Shaposhnik
2008-12-19 16:44 ` ron minnich
2008-12-19 19:21 ` Anthony Sorace
2008-12-19 19:31 ` erik quanstrom
2008-12-19 19:41 ` ron minnich
2008-12-19 19:59 ` Roman Shaposhnik
2008-12-19 20:06 ` erik quanstrom
2008-12-19 20:18 ` Charles Forsyth
2008-12-21 5:08 ` Roman V. Shaposhnik
2008-12-19 3:03 ` Roman Shaposhnik
2008-12-19 3:43 ` erik quanstrom
2008-12-19 3:54 ` Roman Shaposhnik
2008-12-19 4:13 ` geoff
2008-12-19 8:23 ` Russ Cox
2008-12-19 19:49 ` Roman Shaposhnik [this message]
2008-12-19 19:56 ` erik quanstrom
2008-12-19 20:10 ` Roman Shaposhnik
2008-12-19 20:22 ` erik quanstrom
2008-12-19 20:02 ` ron minnich
2008-12-19 14:21 ` erik quanstrom
2008-12-19 21:00 ` ron minnich
2008-12-19 21:32 ` Charles Forsyth
2008-12-19 21:29 ` ron minnich
2008-12-21 5:05 ` Roman V. Shaposhnik
2008-12-21 14:45 ` erik quanstrom
2008-12-22 10:02 ` roger peppe
2008-12-25 6:04 ` Roman Shaposhnik
2008-12-25 6:33 ` erik quanstrom
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=F82C3E5D-D4C2-402A-948B-B2DBA766A6EC@sun.com \
--to=rvs@sun.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).