From: "Alyssa M via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: [9fans] Name duplication in union directories
Date: Sat, 4 May 2024 17:44:54 -0400 [thread overview]
Message-ID: <17148590940.ffce.17300@composer.9fans.topicbox.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Is the presence of the duplicate names when reading a union directory actually needed/used anywhere? Or is it just an artefact of the most straightforward implementation for Plan 9?
I ask because I'm implementing the Plan 9 system calls on my own OS. If I don't have to implement the name duplication in union directories, then I may be able to get away with less code.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tf4c3dc658874afea-M65300584831da4f8f8d56134
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 1132 bytes --]
next reply other threads:[~2024-05-04 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-04 21:44 Alyssa M via 9fans [this message]
2024-05-04 21:46 ` Charles Forsyth
2024-05-05 9:56 ` Alyssa M 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=17148590940.ffce.17300@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).