From: "Alyssa M via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] openat()
Date: Sat, 6 Apr 2024 15:24:24 -0400 [thread overview]
Message-ID: <17124314640.ceA1.70581@composer.9fans.topicbox.com> (raw)
In-Reply-To: <17123735270.469FFd7.853634@composer.9fans.topicbox.com>
[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]
Moody wrote:
"What you _would_ want for this would be the ability to walk from the existing fd, however the limits of 9p walk make this a bit impossible to implement in a great way in my opinion. "
Maybe the chan could keep two fids: the original walked fid, and an opened clone of that fid? The open one could be used for read/write, etc, and the original could be used for subsequent walks.
Ron Minnich wrote:
"The question I had was, can I get the benefit of *at without doing
what linux is doing, namely, for all system calls with a path, make an
'...at' version.
I am guessing so, though I'm not sure it's as efficient."
Could you do something like
open ("/fd/5/as-dir/a/b/c", ...)
or
open ("#d/5/as-dir/a/b/c", ...)
where 5 is the file descriptor of an open directory, and "as-dir" is effectively bound to the directory it has open?
The Linux docs make passing reference to "tricks involving /proc/../fd" which seems like a better idea than adding all those *at system calls...
... from the department of partly-baked ideas...
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T675e737e776e5a9c-M4f2926b33d54b9f6842c2078
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2112 bytes --]
next prev parent reply other threads:[~2024-04-06 19:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 19:50 ron minnich
2024-04-05 20:12 ` Gorka Guardiola
2024-04-05 20:15 ` Gorka Guardiola
2024-04-05 20:36 ` Gorka Guardiola
2024-04-05 21:22 ` ron minnich
2024-04-05 21:43 ` Bakul Shah via 9fans
2024-04-05 21:49 ` Alyssa M via 9fans
2024-04-05 22:29 ` Gorka Guardiola
2024-04-06 3:18 ` moody
2024-04-06 17:35 ` ron minnich
2024-04-06 19:23 ` David Leimbach via 9fans
2024-04-06 19:54 ` Bakul Shah via 9fans
2024-04-06 19:24 ` Alyssa M via 9fans [this message]
2024-04-06 20:51 ` moody
2024-04-07 1:36 ` Alyssa M via 9fans
2024-04-07 15:00 ` Alyssa M via 9fans
2024-04-10 12:17 ` wb.kloke
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=17124314640.ceA1.70581@composer.9fans.topicbox.com \
--to=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).