9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: steve.simon@snellwilcox.com
To: 9fans@cse.psu.edu
Subject: [9fans] 9p questions
Date: Wed, 23 Jul 2003 12:13:59 +0100	[thread overview]
Message-ID: <8db6ea68d1cba1bc0b101c4471e45e32@yourdomain.dom> (raw)

Hi,

two questions about 9p semantics:

1/
Netware will not let me rename a file which is open.

So, when wstat updates a file's name does 9p place a
restriction on wether the file is open or not?

Do I have to do a close, rename and reopen on rename
or is just close safe? I guess the answer is reopen
the file - more races :-(

Netware has similar restrictions on deleteing files/dirs so
I am closing then also,  but I cannot imagine any side
effects from this.

2/
Netware changes its file ID (which I map to Qid) when
a file is renamed.

Using lib9p is it OK to change fid->qid in wstat, under the
libraries feet so to speak?

Also, will it mess up plan9 clients?

-Steve



             reply	other threads:[~2003-07-23 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 11:13 steve.simon [this message]
2003-07-23 14:59 ` rog
     [not found] <599525253@snellwilcox.com>
2003-07-23 15:15 ` steve.simon

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=8db6ea68d1cba1bc0b101c4471e45e32@yourdomain.dom \
    --to=steve.simon@snellwilcox.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).