From: "Bakul Shah via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] openat()
Date: Fri, 5 Apr 2024 14:43:20 -0700 [thread overview]
Message-ID: <79953545-3E92-4A48-AA6E-D20B9AD96463@iitbombay.org> (raw)
In-Reply-To: <CAP6exYLifv8_ujLxN4wEq+PQuJcDmM8zH9KwVh+czoZSMWDrXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2072 bytes --]
To me this sounds very similar to open() given a path relative to your current working directory.
> On Apr 5, 2024, at 2:22 PM, ron minnich <rminnich@gmail.com> wrote:
>
> not so much what I want, I'm curious about ideas people have about implementing it that I would not think of.
>
> On Fri, Apr 5, 2024 at 1:38 PM Gorka Guardiola <paurea@gmail.com <mailto:paurea@gmail.com>> wrote:
>> Hmm sorry. Now I see what you want. Not to rewalk. You can use the chan of the dirfd and walk just the remainder cloning it and creating a new one. That way the openat provides the guarantees you want.
>>
>> On Fri, Apr 5, 2024, 22:15 Gorka Guardiola <paurea@gmail.com <mailto:paurea@gmail.com>> wrote:
>>> I mean, if you want a new syscall jus copy or call the implementation of these.
>>>
>>>
>>> On Fri, Apr 5, 2024, 22:12 Gorka Guardiola <paurea@gmail.com <mailto:paurea@gmail.com>> wrote:
>>>> ¿Isn't that fd2path, strcat and open?
>>>> Or am I misunderstanding something?
>>>>
>>>> On Fri, Apr 5, 2024, 21:51 ron minnich <rminnich@gmail.com <mailto:rminnich@gmail.com>> wrote:
>>>>> One of the folks I worked with, when we pulled a big chunk of plan 9 into akaros, commented that he had implemented openat on akaros.
>>>>>
>>>>> I don't want this to turn into a debate on the merits of openat; I am more curious: if you went to implement openat on Plan 9, how would you go about it? I have a few ideas but I'm more interested in your ideas.
>>>>>
>>>>> Thanks
>
> 9fans <https://9fans.topicbox.com/latest> / 9fans / see discussions <https://9fans.topicbox.com/groups/9fans> + participants <https://9fans.topicbox.com/groups/9fans/members> + delivery options <https://9fans.topicbox.com/groups/9fans/subscription>Permalink <https://9fans.topicbox.com/groups/9fans/T675e737e776e5a9c-M0445ed55bee993d4cfbd3450>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T675e737e776e5a9c-M0efc38028930341e0db8f794
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 3709 bytes --]
next prev parent reply other threads:[~2024-04-05 21:43 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 [this message]
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
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=79953545-3E92-4A48-AA6E-D20B9AD96463@iitbombay.org \
--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).