From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A few questions about 9p
Date: Thu, 29 Jan 2015 10:07:51 +0000 [thread overview]
Message-ID: <CAOw7k5gTK2U2-FBbgHnEmZAG29Aa-OXBtzFZcgKREX8x0YUgMA@mail.gmail.com> (raw)
In-Reply-To: <CAHL7psGsJHNBJWwnHzxMDO3ULe+9=crcbB8F4ML41HDBKYLppA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On 29 January 2015 at 09:04, Giacomo Tesio <giacomo@tesio.it> wrote:
> What's the meaning of qids? I see that responses often include them but
> request messages do not.
>
see intro(5) or intro(9P) depending on system. They identify a file on
a server; they are a value provided by the server to the client,
so they only appear in replies.
> What's the proper message sequence to delete a file? And to delete a non
> empty directly?
>
You point a fid at the file, then remove it: Twalk* ... Tremove
A non-empty directory can't be removed.
Tremove implies Tclunk
> Is it possible to move a file between different directories atomically?
>
No.
> I can't find details on the file execution permission: looks like a
> malicious client could just ignore it on files and execute anything that it
> can read (obviously I'm just talking about single files, not directory).
>
It's not malicious, just incorrect. Obviously you can't execute a
remote image or script unless you read it.
The existing servers treat OEXEC as opening for read, with a check of
the X permission.
A directory, however, can't be opened OEXEC.
In the script case, the file server will allow the OEXEC open, but
#!interpreter is converted to {interpreter file},
and then if the file is x-only, the subsequent open for OREAD will
fail. Possibly the interpreters should open OEXEC, but they don't.
> When I should clunk the afid?
>
When the client closes it.
> What about encryption? Is it completely delegated to the transport layer?
>
Yes, for encryption of communication. A file server could encrypt
files or the whole storage structure.
[-- Attachment #2: Type: text/html, Size: 2825 bytes --]
next prev parent reply other threads:[~2015-01-29 10:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHL7psHNZrbQuFRz5grmXgR686o2e+-SX=tW6yxnfNaduec5NQ@mail.gmail.com>
[not found] ` <CAHL7psGPf3z56wjZGJsSVCeEzHBJgtbt17nL-UNA8kXKM-mkuw@mail.gmail.com>
[not found] ` <CAHL7psFTR7G1N069XoqYkuxJ_P0TYzmXAZ752wVa=9BAOX0CQg@mail.gmail.com>
[not found] ` <CAHL7psEUjdaV9LABzRrHn1TLftF+moxWV563-tvK+7VLviKhRg@mail.gmail.com>
2015-01-29 9:04 ` Giacomo Tesio
2015-01-29 10:07 ` Charles Forsyth [this message]
2015-01-29 14:36 ` erik quanstrom
2015-01-29 14:41 ` Giacomo Tesio
2015-01-29 14:52 ` erik quanstrom
2015-01-29 14:54 ` cinap_lenrek
2015-01-29 15:46 ` Giacomo Tesio
2022-10-31 23:14 ibrahim via 9fans
2022-11-04 23:41 ` ron minnich
2022-11-05 1:32 ` ibrahim via 9fans
2022-11-05 4:10 ` ibrahim via 9fans
2022-11-05 4:30 ` ori
2022-11-05 6:30 ` ibrahim via 9fans
2022-11-05 14:09 ` ori
2022-11-05 15:50 ` ibrahim via 9fans
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=CAOw7k5gTK2U2-FBbgHnEmZAG29Aa-OXBtzFZcgKREX8x0YUgMA@mail.gmail.com \
--to=charles.forsyth@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).