From: "Alejo Sanchez" <alejos@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] 9P and locking
Date: Tue, 31 Oct 2006 14:25:47 +0000 [thread overview]
Message-ID: <3190d0e50610310625s6a571ca3ne7150d46a86ac297@mail.gmail.com> (raw)
In-Reply-To: <3190d0e50610250505j723f392fp319da7ff20adc313@mail.gmail.com>
Hi guys.
I'm doing a minimal user space 9P implementation for a special
distributed network storage. One of the features missing on the 9P
protocol is file locking. Do you know why it was kept outside? Or am I
missing something?
So far my plan to extend is to have messages mimicking fcntl, but
maybe that's not the best way to get it done. Did anyone work on
locking and would like to share their experience or opinion?
Cheers.
Alejo
next parent reply other threads:[~2006-10-31 14:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3190d0e50610250505j723f392fp319da7ff20adc313@mail.gmail.com>
2006-10-31 14:25 ` Alejo Sanchez [this message]
2006-10-31 14:36 ` Bruce Ellis
2006-10-31 14:39 ` Anel Philippe
2006-10-31 14:44 ` Bruce Ellis
2006-10-31 15:16 ` Charles Forsyth
2006-10-31 16:09 ` Bruce Ellis
2006-10-31 16:11 ` Alejo Sanchez
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=3190d0e50610310625s6a571ca3ne7150d46a86ac297@mail.gmail.com \
--to=alejos@gmail.com \
--cc=9fans@cse.psu.edu \
/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).